On Sun 25 Feb 2007, Brandon Barnes wrote: > > Rsync daemon fails silently. To reproduce:
The problem is probably that you don't have a /etc/rsyncd.conf file. Rsync will log this to syslog and then exit. > Expected behavoior is either rsync running, or an error message saying > why it is not running. The problem is that rsync first detaches itself into a daemon, and then finds the problem. At that point, connection with the terminal is lost. The only option for rsync then is to log to syslog. The need for the rsyncd.conf was documented in README.Debian, unfortunately due to an oversight on my part this file was not included in the distribution. Of course, wanting to start a daemon without having a configuration available for it isn't that sensible :-) I'm in doubt as to how easy this is fixable, and if upstream wants to. It will probably mean a pretty large change to the program flow for the daemon, for little advantage (for those who know what they're doing :) I agree however that the init.d restart should have shown something, I'll look into that. Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
