I have received a few queries regarding my progress in solving the rsync
sender's abortive connection close() on Winsock-based platforms. In my
research, I stumbled across articles that implied that Microsoft is not the
only OS vendor that provides platforms that may exhibit this problem. I am
> I'm a little surprised at this. I use rsync on Win2k every day. Runs
> automatically at 1pm in my case, and it hasn't bombed yet. Win2k is the
> "sender", receiver is Linux 2.2.13-0.9. Both have rsync 2.4.6. cygwin is
> a little old on win2k, uname -a returns 1.1.2. Linux is running sshd
>
I'm a little surprised at this. I use rsync on Win2k every day. Runs
automatically at 1pm in my case, and it hasn't bombed yet. Win2k is the
"sender", receiver is Linux 2.2.13-0.9. Both have rsync 2.4.6. cygwin is
a little old on win2k, uname -a returns 1.1.2. Linux is running sshd
version 1
"OMeara, Randy" <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> ...
> Research and experimentation indicates that the cause of this symptom is the
> timing and manner in which the sender's socket is closed. ...
>
> I believe a proper fix would require a modification of the rsync protocol
Actually, a
Hi All,
I posted a query here (5/22/01) concerning problems with rsync on Windows
2000. I want to partially answer my own question, see if anyone has already
solved this problem, and seek additional guidance in designing a fix.
It appears that, when rsync on W2K is the 'sender', the rsync recei
