Neil Schellenberger on Tue 17/10 23:55 -0400:
> In particular, is anyone who is using --timeout=0 (the default) on the
> server nonetheless seeing unexpected EOF?
It's been a while, but to my recollection, yes, I didn't (never have)
set any timeout values, but I still got this error at seemingly random
places when transferring large (== starting at a few hundred megs)
groups of files, using ssh as the transport (although it works when ssh
is compiled to use socketpair() instead of pipe()) The only thing that
fixes it for me reliably is the buffer hack in io.c from 2.3.something
(the one that says "uuggh" in the comments and was later removed on
grounds of being a kludge). When using this version of io.c it works
every time on arbitrarily large data sets (my biggest test was a few
dozen gigs), whether ssh was compiled to use pipes or socketpairs.
