X-Spam-Check-By: sourceware.org Date: Wed, 21 Dec 2005 12:27:45 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Listening sockets not always closing? Message-ID: <20051221112745.GA28865@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Dec 20 19:23, Craig Davison wrote: > 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? I can't. Your testcase works fine on my W2K SP4 test system. As for earlier Service Pack stages, I can't tell for the lack of a test system. As Larry mentioned, http://cygwin.com/acronyms/#PTC. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/