rsync - Jun 2002 - rsync: error writing NNNN unbuffered bytes - exiting:Connection reset by peer

Has anyone figured out what is happening with this error?  There are
many reports of this, but the advise seems to fall short - ie. make sure
you are using rsync 2.5.n, make sure the target disk is not full.

I have used rsync 2.5.[1,2,4,5] on my rsync server, and I get the same
results.  The target disk I am working with never gets more than 2% full
when the rsync client and server quit talking to each other.  I'm using
a 2.4.18 Linux kernel(both), ext2 filesystems (both).  Networking is
100Mbit, each NIC card is Realtec 8139too driver compatible.

I've tried adding the '--bwlimit=NNNN' and '--blocking-io'
options when
invoking the client rsync, but neither affects the result.

Suggestions on how to proceed would be greatly appreciated.

Thanks
-- 
Bill Geddes                            
  bill_geddes@agilent.com

-- 
"I had a fortune cookie the other day and it said: 'Outlook not
so good'. I said: 'Sure, but Microsoft ships it anyway'."

On 13 Jun 2002, Bill Geddes wrote:
> Suggestions on how to proceed would be greatly appreciated.
It is possible that one side of the connection is seg-faulting and
dying.  If you ensure that core files are not disabled (check your
ulimit setting), you may find that there is a core file that you could
use to figure out where the program is dying.  Alternately, you could
attach to one or both processes with a debugger after it starts running
(e.g. "gdb /usr/bin/rsync 12345" where "12345" is the
already-running
process ID), tell it to 'c'ontinue to run, and you'll see any
abnormal
signals that may pop up.

..wayne..