Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <414191AC.8A4E2B31@dessent.net>
Date: Fri, 10 Sep 2004 04:36:12 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: rsync + xp sp2 failing
References: <20040909202553 DOT 8B672E598 AT wildcard DOT curl DOT com> <4140C972 DOT 6030408 AT iwcenter DOT com> <20040909220929 DOT GA30475 AT cygbert DOT vinschen DOT de> <41416396 DOT 48B2E11E AT dessent DOT net> <20040910084618 DOT GU17670 AT cygbert DOT vinschen DOT de> <2899 DOT 10 DOT 0 DOT 0 DOT 7 DOT 1094815161 DOT squirrel AT mail DOT equate DOT dyndns DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Chris Taylor wrote:

> Is it possible this is due to the changes in tcpip.sys and/or the tcp
> stack? I myself am using a hacked one without these changes, so I could
> test things to see if it is, if people can give me a specific set of
> things to do ;-)
> Unfortunately, half of the stuff in this thread went clean over my head,
> so I could easily be barking up the wrong tree....

The change he's referring to is the limit in SP2 meant to catch worms
and malware that connect to random IP addresses.  MS's fix was to
throttle the TCP/IP stack when it reaches 10 outgoing half-open
connections.  Note: that's not 10 connections total, that's 10 half-open
connections, i.e. state SYN_SENT.  This only really happens when you try
to open a bunch of simultaneous connections to non-existant / dark IP
space, which is typical of a worm.  However I doubt that rsync could
possibly trigger this state, so it's likely not relevant.  Nor are the
changes regarding raw sockets.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/