X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<20110130221219.GH1057@calimero.vinschen.de>
References:	<AANLkTi=HunjC3MPZo37xZ8Yd1Mh1329yD5sQDfaNJWG9 AT mail DOT gmail DOT com> <20110130221219 DOT GH1057 AT calimero DOT vinschen DOT de>
Date:	Mon, 31 Jan 2011 17:12:48 +0100
Message-ID:	<AANLkTinQaRH98zR_TkrcBhgP2qU+RL9vkzMyg89rhXXv@mail.gmail.com>
Subject:	Re: Issue with socket SO_REUSEADDR when a client is connected.
From:	jdzstz - gmail dot com <jdzstz AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

>
> The Cygwin workaround to fix the WinSock SO_REUSEADDR behaviour from
> back in 2006 was not so nifty after all. =A0I just fixed that in CVS. =A0=
I'm
> going to generate a new developer snapshot right now. =A0Should be up in a
> couple of minutes.
>

Using cygwin snapshot, the testcase and varnishtest program works fine.

This bugfix will be included in cygwin 1.7.8 ?

There is any estimated release date for cygwin 1.7.8?

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

- Raw text -