Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <00b801c23744$49ec4540$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: "Nicholas Wourms" <nwourms AT netscape DOT net>
Cc: <cygwin-developers AT cygwin DOT com>
References: <010901c23724$96e5d430$6132bc3e AT BABEL> <3D4581E4 DOT BB580995 AT ieee DOT org> <005801c23730$02304170$6132bc3e AT BABEL> <3D459257 DOT 240C79DC AT ieee DOT org> <009c01c23736$4a61a4b0$6132bc3e AT BABEL> <3D45A95A DOT 10207 AT netscape DOT net>
Subject: Re: TCP problems
Date: Mon, 29 Jul 2002 22:09:52 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

"Nicholas Wourms" <nwourms AT netscape DOT net> wrote:
> Perhaps we could implement a counter to ascertain exactly how
many
> cycles until dies?  Either that or I could pipe netstat to a
file and
> have nano count how many open sockets there are...  That figure
should
> not be taken as exact, due to the fact I didn't run 'time' and
was
> guessing when you asked.

You could run the client through (something like):

    client <xxx> | grep 'connect' | wc

But I was more interested in the error codes than in the exact
number of sockets. That can be affected by lots of things, such as
registry parameters.

Also my guess is that on your system, the last connect was to
socket 4999 or 5000?  Especially with the EADDRINUSE error that
you got at another point, which probably indicates that all the
temporary sockets (1024-5000 ?) were in TIME_WAIT state.  I can't
ever hit that problem, 'cos my computer's not quick enough :-(
[just guessing here].

BTW, what was the machine set up for this? (windows version,
memory size?).

// Conrad