This smacks of the abortive socket closure symptoms I've seen
and mentioned on this list. It occurs when the NT/2K side is
the sender.
Randy O'Meara
> -----Original Message-----
> From: Greg Walton [mailto:greg@sextant.com]
> Sent: Tuesday, August 14, 2001 11:48 AM
> To: rsync@lists.samba.org
> Subject: Re: EOF erors
>
>
>
> ----- Original Message -----
> From: "Randy Kramer" <rhkramer@fast.net>
> To: "Greg Walton" <greg@sextant.com>
> Cc: <rsync@lists.samba.org>
> Sent: Tuesday, August 14, 2001 9:43 AM
> Subject: Re: EOF erors
>
>
> > Greg Walton wrote:
> > >
> > > I am new to using rsync so I apologize if this has been answered
> > > before. I still get and unexpected EOF in read_timeout
> error after I
> > > apply all the patches. Is there another fix that I can
> try? Thanks
> > >
> > > greg
> >
> > What are you trying to do? Are you trying to rsync a large file?
> >
> > I've had trouble like this rsyncing large files. The
> problem seemed to
> > be that the server took so long to process the file before sending
> > anything that, AFAICT, another part of the server decided
> the process
> > was dead and killed it. IIRC, I solved my problem by removing some
> > options that added to the processing time, like "-c".
> >
> > Hope this helps,
> > Randy Kramer
> >
>
> Thanks for your help so far. I can copy to my Win 2000 box
> but I get a read
> error: Connection reset by peer error when I try to put files
> on my win 2000
> box to my Unix box.
>
> greg
>
>