Your message dated Mon, 28 Apr 2008 12:58:54 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#476182: rsync: fails to start
has caused the Debian Bug report #476182,
regarding rsync: fails to start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
476182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476182
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
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: /bin/sh linked to /bin/bash
Versions of packages rsync depends on:
ii base-files 4.0.3 Debian base system miscellaneous f
ii libacl1 2.2.45-1 Access control list shared library
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libpopt0 1.10-3 lib for parsing cmdline parameters
ii lsb-base 3.2-8 Linux Standard Base 3.2 init scrip
rsync recommends no packages.
-- no debconf information
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 exists (17)
2008/04/15 00:13:19 [15022] rsync error: error in file IO (code 11) at
clientserver.c(991) [receiver=3.0.2]
--- End Message ---
--- Begin Message ---
> Thanks, kicking out the pid file solves my problem. Next time I'll first do
> some rtfm ;-)
> Just wonder about, because I've ued the pid file since more than 1 year and
> never got any problems.
> Did I miss any debconf dialog or was there never any suggestions to check the
> rsyncd.conf?
The new version is probably more picky about the pid file;
besides that the handling hasn't changed.
Now closing this bug report.
Paul Slootman
--- End Message ---
