I got around this by using the --temp=/SomeLargeFreeDir
But again - its getting around it not fixing it.
Dale
--- [EMAIL PROTECTED] wrote:
> I'm seeing this problem too, and the problem isn't the
> amount of data or number of files transferred. It's the
> number of files examined. It'll fail r
I had the same error this is what fixed it for me
/usr/bin/rsync -avc --stats --timeout=0 \ Hostname:/source/
/TargetOnLocalHost
Note the --timeout and you can also speed the process
up by dropping the c from the -avc.
Hope this helps
Dale
--- Wileczek_Mickaël <[EMAIL PROTECTED]>
wrote:
>
Thank you very much this is a very plausiable cause.
It is a very large filesystem. thanks again.
--- Alberto Accomazzi <[EMAIL PROTECTED]> wrote:
>
> The "unexpected EOF in read_timeout" can happen for a
> variety of reasons,
> but it typically shows up when you have deadlock (no
> bytes sent
I agree. I am going to check the aix ulimit
params as it is a stock box and no mods have
been made yet.
thanks
Dale
--- Michael <[EMAIL PROTECTED]> wrote:
> > Dale Phillips wrote:
> >
> > > I am trying to rsync a rather large amount of
> > > data.
> 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
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
&g
Hello,
I am trying to rsync a rather large amount of
data. (i.e. clone a box) - What causes the
unexpected EOF in read_timeout?
thanks in advance
Dale
__
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.ya
