Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3C5080F8.4E4B8945@ieee.org>
Date:	Thu, 24 Jan 2002 16:47:36 -0500
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
X-Mailer:	Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language:	en,pdf
MIME-Version:	1.0
To:	Corinna Vinschen <cygwin AT cygwin DOT com>
Subject:	Re: socket/fdopen/exec problem
References:	<3C50520B DOT 3239FAC5 AT ieee DOT org> <20020124220339 DOT K11608 AT cygbert DOT vinschen DOT de>

Corinna Vinschen wrote:

> Isn't that just the usual effect that sockets remain in TIME_WAIT
> state for 2MSL seconds?

I realize I am mixing two things. Seeing reused ports in netstat
isn't much of a problem in itself, as long as new calls can come
in. That's the OK case I see now all the time on NT. However the
problem I am chasing (on Win98) is that new calls are not accepted.
I will clarify and get back to you.

Pierre

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -