push data instead of pull

tim.conway at philips.com tim.conway at philips.com
Thu Feb 21 08:38:19 EST 2002

That was my point.  ro and rw were both /tmp.  i made ro first, tested it, 
duplicated Gautam's error, copied it, changed "yes" to "no" on the "read 
only = " line, and got success.  The really odd thing was tht i got 
meaningful error on ro if i was tracing the rsyncd (started as "truss -f 
rsync --daemon", "-f" meaning follow forks).  I'd suppose that slowed the 
daemon slightly in some way, alleviating a race condition. 

Tim Conway
tim.conway at philips.com
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn, 
".\n" '
"There are some who call me.... Tim?"

Martin Pool <mbp at samba.org>
02/20/2002 12:23 PM

        To:     Tim Conway/LMT/SC/PHILIPS at AMEC
        cc:     Gautam Ganesh <gaudam at yahoo.com>
rsync at samba.org
        Subject:        Re: push data instead of pull

> >rsync rsync.h alta::ro
> rsync: read error: Connection reset by peer
> rsync error: error in rsync protocol data stream (code 12) at io.c(151)

"Connection reset by peer" often means the remote rsync crashed. 

If you see this message when the only problem is that the remote
module is read only, that's a bug.


More information about the rsync mailing list