X-Spam-Check-By: sourceware.org
Date: Tue, 20 Dec 2005 19:23:26 -0700 (MST)
From: Craig Davison <craig AT darkcalgary DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Listening sockets not always closing?
In-Reply-To: <Pine.BSO.4.58.0512201358150.21488@www.darkcalgary.com>
Message-ID: <Pine.BSO.4.58.0512201917190.13902@www.darkcalgary.com>
References: <Pine DOT BSO DOT 4 DOT 58 DOT 0512201358150 DOT 21488 AT www DOT darkcalgary DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

Hate to reply to my own message, but I missed something...

On Tue, 20 Dec 2005, Craig Davison wrote:
> I created a small test program to illustrate this. Basically, in a loop, I
> create a SOCK_STREAM socket, call bind() and then listen(), check the
> output of netstat, and then close the socket. It works on several
> versions of Linux, and Windows >= 2000 SP 2, but bind fails with
> EADDRINUSE the second time through the loop on Windows <= 2000 SP1.

It appears that the test program fails with up to Windows 2000 SP4.
Windows XP still works. My observation that SP3/SP4 worked was based on
some production code where I first saw this problem, not the minimal test
code I posted here. Sorry for the confusion.

Can anyone with Win 2000 SP4 reproduce this?
Thanks

--
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/