X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sun, 30 Jan 2011 23:12:19 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Issue with socket SO_REUSEADDR when a client is connected. Message-ID: <20110130221219.GH1057@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=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 Jan 30 15:31, jdzstz - gmail dot com wrote: > I have detected an issue in windows xp with socket SO_REUSEADDR when a > tcp client keeps connected forever. > > I don't know if it is a cygwin bug or a problem with microsoft winsock > implementation. I don't know if windows vista or windows 7 has the > same behaviour. Thanks for the testcase. I was going to go to great lengths explaining how WinSock has a bug in SO_REUSEADDR behaviour and how Cygwin has a nifty workaround for this, but I got a bad feeling while writing my reply and started a cycle 1. test 2. read MSDN 3. scratch head 4. debug 5. change 6. goto 1 The Cygwin workaround to fix the WinSock SO_REUSEADDR behaviour from back in 2006 was not so nifty after all. I just fixed that in CVS. I'm going to generate a new developer snapshot right now. Should be up in a couple of minutes. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple