On 17 Oct 2000, Jan?ke R?nnblom <[EMAIL PROTECTED]> wrote:
> Hi!
>
> Tried to use rsync-2.4.6 from my windows 2000 machine without
> ssh support and running a daemon on the unix host. I also get this
> when running from unix to unix. This is what i get after a while in
> my log files:
>
>
> Oct 17 15:21:13 rsync rsyncd[6442]: transfer interrupted (code 30)
> at io.c(65)
> Oct 17 15:21:13 rsync rsyncd[6458]: transfer interrupted (code 20)
> at main.c(663)
>
> which is?
>
> errcode.h:#define RERR_TIMEOUT 30 /* timeout in data
> send/receive */
>
> What does this mean? Could there be a problem with my network
> lines going up/down? Would a network problem trigger this kind of
> behavior?
Yes, it probably indicates a network problem. Are the two machines
close together, or are they connected by a slow or unreliable line?
You can try passing a large value to the --timeout option to make it
more tolerant of slow connections, but obviously if the network has
actually gone altogether that won't help.
It would be interesting to see the output of netstat -t and therefore
whether the TCP connection has actually dropped.
> Or does rsync automatically resend/reconnect?
rsync will not automatically try to recover, although your TCP stack
will of course retransmit for a certain time. However, because rsync
always tries to bring the two directories into synchronization, you
can just retry the transfer either by hand or by a script until it
completes.
--
Martin Pool, Linuxcare, Inc.
+61 2 6262 8990
[EMAIL PROTECTED], http://www.linuxcare.com/
Linuxcare. Support for the revolution.
PGP signature
