Just to try and remove some possible problems, have you tried doing it through
ssh instead?  Then you don't need to bother setting up the server.

rsync -e ssh ...


Ben Kochie <ben at nerp.net> writes:

> ok.. this is a _really_ wierd problem.. I'm running a NetBSD 1.4 web
> server, and I am trying to setup an rsyncd server on it so i can mirror
> off the data to our shiny new penguin computing box.  but whenever I try
> and start the rsync session from the linux box, i get this message on the
> NetBSD server.
> 
> Jul 18 15:17:49 silver rsyncd[13318]: rsync on blah/ from systems@(host)
> Jul 18 15:17:49 silver rsyncd[13318]: transfer interrupted (code 3) at
> main.c(263)
> 
> and on the client end I get this:
> 
> $ rsync -azrvl --progress  --password-file=/root/pass --progress
> systems at silver::blah/ /web
> receiving file list ... push_dir rsyncd: No such file or directory (3)
> unexpected EOF in read_timeout
> 
> here's what my rsyncd.conf looks like:
> [blah]
> path = /web
> auth users = systems
> secrets file = /etc/rsyncd.secrets
> 
> 
> I have no idea what the heck is causing this.. I tried setting up a
> similar rsync server on the linux box.. and I got the same messages when I
> try and sync from the netbsd server.. but when I run the same exact
> command on another linux box.. it works fine.. ARG!
> 
> Thank You,
>         Ben Kochie (ben at nerp.net)
> 
>  "Unix is user friendly, Its just picky about its friends."
> 
> 
> _______________________________________________
> tclug-list mailing list
> tclug-list at mn-linux.org
> https://mailman.mn-linux.org/mailman/listinfo/tclug-list

-- 
Jon Schewe | http://mtu.net/~jpschewe | jpschewe at mtu.net
For I am convinced that neither death nor life, neither angels 
nor demons, neither the present nor the future, nor any 
powers, neither height nor depth, nor anything else in all 
creation, will be able to separate us from the love of God that 
is in Christ Jesus our Lord. - Romans 8:38-39