Folks,
Just in case there is any doubt remaining: yes, I am an idiot.
As was probably obvious to everyone but me, in the specific case that
I have bored everyone to tears with, I am running afoul of a feature
that I myself enabled (i.e. timeouts). That is to say, the analysis
was correct, but
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
> On 18 Oct 2000, Martin Pool <[EMAIL PROTECTED]> wrote:
> > On 17 Oct 2000, Jan?ke R?nnblom <[EMAIL PROTECTED]> wrote:
> > > Hi!
> > >
> > > Recap:
> > > Im trying to syncronize my Windows NT servers to a central unix
> > > box running redhat 7.0. Previously I falsely stated that rsync 2.3.2
