Maybe the daemon is running but I don't think so: mkb@veri:/var/log$ ps -elf|grep rsync 0 S mkb 24869 21866 0 80 0 - 17433 pipe_w 15:26 pts/4 00:00:00 grep rsync and this is when I've tried both of a) /usr/bin/rsync --daemon -v b) sudo /sbin/chkconfig rsync on I also see, when trying to see which rsync modules are loading, the follow error message (when invoked from another machine): # rsync veri.phy.umist.ac.uk:: rsync: failed to connect to veri.phy.umist.ac.uk: Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(104) [receiver=2.6.9] Please could somebody let me knw what I'm going wrong? Ta, MIchael
On Thu, 2008-10-09 at 15:29 +0100, michael wrote:> Maybe the daemon is running but I don't think so: > > mkb@veri:/var/log$ ps -elf|grep rsync > 0 S mkb 24869 21866 0 80 0 - 17433 pipe_w 15:26 pts/4 > 00:00:00 grep rsync > > and this is when I've tried both of > a) /usr/bin/rsync --daemon -v > b) sudo /sbin/chkconfig rsync onFedora does not provide an initscript for rsync, so you should be using command (a). You need to write an /etc/rsyncd.conf file if you haven't already; see the rsyncd.conf(5) man page for details. If the daemon still won't start, check the log file you defined in /etc/rsyncd.conf or the syslog in /var/log/messages to find out why. Matt
On Thu, Oct 09, 2008 at 03:29:04PM +0100, michael wrote:> and this is when I've tried both of > a) /usr/bin/rsync --daemon -v > b) sudo /sbin/chkconfig rsync onFedora supplies an /etc/xinetd.d/rsync file that defaults to off. Using your b command should turn it on and sighup xinetd. If you go the xinetd route, that means that there won't be a dedicated rsync daemon running. You could elect to leave the xinetd config file disabled and run a daemon, if you like. However, Fedora doesn't supply an /etc/rsyncd.conf file, which you must create for rsync to work. With that set you should be able to run a "telnet localhost 873". If not, check the xinetd config files (if used). You can also try a "rsync --daemon --no-detach" to see if it outputs any errors about your config file (it can output some errors that way that can't make it into a log file, such as permission errors trying to create the log file). Hit Ctrl-C to kill it if it didn't die due to an error (an inability to bind error would be expected if you left xinetd enabled). ..wayne..