My first rsync experience

Dave Dykstra dwd at
Thu Dec 5 21:16:00 EST 2002

First, as a newbie you should be aware that a lot of people think they
need to use daemon mode when they can do fine with the much simpler normal
rsh or ssh mode, so make sure you really do need it.  Second, if you do
need it, make sure you can do 'telnet servername 873' and get a response,
otherwise your server isn't running at all; it usually helps to set up a
"log file" and look for errors there.  Third, when the server is running
you'll need to either specify a specific file or pass some options from
the client such as "-a".  When I use the example you gave I get the error

    client: nothing to do: perhaps you need to specify some filenames or the --recursive option?

- Dave Dykstra

On Wed, Dec 04, 2002 at 11:34:02AM -0000, David Flood wrote:
> Before I start let me say I'm a relative newbie to rsync so bear with me. I've just installed 
> version 2.5.5 and set up the following files on the server:
> inetd.conf
> rsync           stream tcp      nowait  root    /usr/local/bin/rsync rsyncd 
> --daemon
> rsync.conf
> [www]
>         path = /test/test2
>         comment = Test
> services
> rsync           873/tcp
> then I run 'rsync --daemon' and that seems to work fineor at least gives no errors 
> although 'ps -ef | grep rsync' does not come back with anything.
> When on another machine I do a 'rsync servername::www .' it produces the following 
> out put:
> rsync: connection unexpectedly closed (0 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12) at io.c(150)
> Can anyone help?
> -----------------------------------------
> David Flood
> Systems Administrator
> dpf at
> Tel: +44 (0)1224 262774
> The Robert Gordon University
> School of Computing
> St. Andrews Street
> Aberdeen
> -----------------------------------------
> -- 
> To unsubscribe or change options:
> Before posting, read:

More information about the rsync mailing list