Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18652 - rsync when run as a daemon writes it's own pid file conflicting with the start-stop script
Attached to Project:
Arch Linux
Opened by Chris Allison (wempy) - Friday, 12 March 2010, 11:56 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 19 March 2010, 19:56 GMT
Opened by Chris Allison (wempy) - Friday, 12 March 2010, 11:56 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 19 March 2010, 19:56 GMT
|
DetailsDescription:
rsync fails to start as a daemon, reporting that it's pid file already exists. The pid file is created, not only by the rsync binary, but by the start-stop script in /etc/rc.d/rsyncd Commenting out the pid file creation line in the start section of the script fixes the issue. Additional info: * package version(s) 3.0.7-1 * config and/or log files etc. Steps to reproduce: run /etc/rc.d/rsyncd start rsync responds with a failure to start as it's pid file already exists. Commenting out the pid file creation line in the start section of the script fixes the issue. |
This task depends upon
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547922
Hope it solves your issue...
The bug should be closed then...