Re: Issue with socket SO_REUSEADDR when a client is connected.

2011-01-31 Thread Larry Hall (Cygwin)
On 1/31/2011 11:12 AM, jdzstz - gmail dot com wrote: 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. Using

Re: Issue with socket SO_REUSEADDR when a client is connected.

2011-01-31 Thread jdzstz - gmail dot com
> > 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. > Using cygwin snapshot, the testcase and varnishtest

Re: Issue with socket SO_REUSEADDR when a client is connected.

2011-01-30 Thread Corinna Vinschen
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

Issue with socket SO_REUSEADDR when a client is connected.

2011-01-30 Thread jdzstz - gmail dot com
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. I have a server process that open a