On Wed, May 30, 2001 at 02:05:33AM -0500, Phil Howard wrote: > > I'm a novice at rsync, so I can't tell you all the details, but, in > > general, the "unexpected EOF in read_timeout" (usually) means that > > something not so good happened on the server side. On what server I was > > connecting to, I believe that the preprocessing by the server made some > > watchdog on the server side decide that the process was dead -- it then > > killed it, and then I got the error message. I never proved this > > completely. > > I posted a while back with this problem and someone answered that the > message existed in ssh and not in rsync. I never verified it. No, that's not correct. That message is in rsync. The message that you're thinking about that is in ssh is Write failed: Cannot allocate memory and that resulted in rsync printing out the "unexpected EOF" message, which can come anytime the connection to the server is lost. - Dave Dykstra
- Re: unexpected EOF in read_timeout Dave Dykstra
- unexpected EOF in read_timeout Dale Phillips
- Re: unexpected EOF in read_timeout Phil Howard
- Re: unexpected EOF in read_timeout Dale Phillips
- Re: unexpected EOF in read_timeout Michael
- Re: unexpected EOF in read_timeout Dale Phillips
- Re: unexpected EOF in read_timeout Randy Kramer
- Re: unexpected EOF in read_timeout Dale Phillips
- Re: unexpected EOF in read_timeout Phil Howard
- Re: unexpected EOF in read_timeout Dave Dykstra
- Re: unexpected EOF in read_timeout Alberto Accomazzi
- Re: unexpected EOF in read_timeout Dale Phillips
- RE: unexpected EOF in read_timeout Allen, John L.
- RE: unexpected EOF in read_timeout Michelle Brownsworth
- RE: unexpected EOF in read_timeout tim . conway
- Re: unexpected EOF in read_timeout willem
- Re: unexpected EOF in read_timeout Eric Whiting
- Re: unexpected EOF in read_timeout Ronan KERYELL
- unexpected EOF in read_timeout David Bordas
- Re: unexpected EOF in read_timeout David Bordas