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.
At the time, because I was new to using rsync, I was using the -c option
to force a full checksum comparison of the two files (because I thought
that the files were not updating because the dates and times matched).
I stopped using the -c option and just made sure the dates and times did
not match and that cured my problem with the "unexpected EOF ..." -- I
believe because the server (and client) spent less time calculating
checksums before starting to exchange data.
(All this is to the best of my recollection.)
Hope this helps!
Randy Kramer
Dale Phillips wrote:
>
> No. I am using aix 4.3 and rsh. I am wondering
> if it is some sort of a network glitch.
> Dale
>
> --- Phil Howard <[EMAIL PROTECTED]> wrote:
> > Dale Phillips wrote:
> >
> > > I am trying to rsync a rather large amount of
> > > data. (i.e. clone a box) - What causes the
> > >
> > > unexpected EOF in read_timeout?
> >
> > I get these. Apparently it is ssh. Are you running this
> > through ssh?
> >
> > --
> >
> -----------------------------------------------------------------
> > | Phil Howard - KA9WGN | Dallas |
> > http://linuxhomepage.com/ |
> > | [EMAIL PROTECTED] | Texas, USA |
> > http://phil.ipal.org/ |
> >
> -----------------------------------------------------------------
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail - only $35
> a year! http://personal.mail.yahoo.com/
