On Tue 15 Apr 2008, Stephan Breitrainer wrote:
Logfile: /var/log/rsyncd.log
2008/04/15 00:13:18 [14920] rsync error: received SIGINT, SIGTERM, or SIGHUP
(code 20) at rsync.c(271)
[receiver=2.6.9]
2008/04/15 00:13:19 [15022] rsync: failed to create pid file
/var/run/rsync.pid: File
Paul Slootman wrote ..
On Tue 15 Apr 2008, Stephan Breitrainer wrote:
Logfile: /var/log/rsyncd.log
2008/04/15 00:13:18 [14920] rsync error: received SIGINT, SIGTERM, or SIGHUP
(code 20) at rsync.c(271)
[receiver=2.6.9]
2008/04/15 00:13:19 [15022] rsync: failed to create pid file
On Tue 15 Apr 2008, Stephan Breitrainer wrote:
sun:~# cat /etc/rsyncd.conf
pid file = /var/run/rsync.pid
You shouldn't use /var/run/rsync.pid if you use the standard
/etc/init.d/rsync script to stop/start rsync (the comments in
/usr/share/doc/rsync/examples/rsyncd.conf specifically state
Paul Slootman wrote ..
On Tue 15 Apr 2008, Stephan Breitrainer wrote:
sun:~# cat /etc/rsyncd.conf
pid file = /var/run/rsync.pid
You shouldn't use /var/run/rsync.pid if you use the standard
/etc/init.d/rsync script to stop/start rsync (the comments in
Package: rsync
Version: 3.0.2-1
Severity: normal
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell:
5 matches
Mail list logo