Hi,
If you are able to rsync over ssh, this connection may be more robust than
plain rsync protocol. See
http://www.mail-archive.com/rsync@lists.samba.org/msg26280.html
Best regards,
Vitorio
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change
error: received SIGINT, SIGTERM, or SIGHUP (code 20)
> at rsync.c(562) [generator=3.0.7]
Something on the local machine sent rsync a signal. Try to figure out
what.
> Subsequent runs =>
>
> [2]
> rsync: read error: Connection reset by peer (54)rsync: writefd_unbuffered
> f
d error: Connection reset by peer (54)rsync: writefd_unbuffered
failed to write 4092 bytes to socket [generator]: Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(1530)
[generator=3.0.7]
rsync error: received SIGUSR1 (code 19) at main.c(1288) [receiver=3.0.7]
fr
