Re: XWin listens on too many TCP ports and killing existing connections.

[Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>]

On Sat, May 29, 2004 at 11:14:17PM +0200, Alexander Gottwald wrote:
>Caphe Noir wrote:
>>From: "Alexander Gottwald"
>><Alexander.Gottwald@s1999.tu-chemnitz.de>
>>>I've created a small testprogram which calls select with a timeout of 1
>>>second.  Get it from
>>>http://www.tu-chemnitz.de/~goal/xfree/select.tar.gz unpack and run it:
>>>/select.exe www.google.com 80
>>>
>>>This will print lines with "timeout".  Do you get a new connection with
>>>every timeout message?
>>
>>Sure does, a new listening connection at every timeout.
>
>Are the connections sticky?  I've just run it on my cygwin installation
>and the number of connections is fixed.  There is a new connection
>every second but the old disappears before the new is created.
>
>If you experience a different behaviour than it must be a problem with
>ZoneAlarm or an other program installed on your host.
>
>>Is there any work-around for this select problem?
>
>I'm directing the message to the cygwin list since this problem also
>occurs with a plain small cygwin program and is not bound to Cygwin/X
>at all.

I think I already mentioned that this is standard cygwin behavior.
There is no reason to rehash it again.  I'm sure that google would be
informative on this subject.

If someone don't like the fact that cygwin opens a listening socket
whenever it uses select then -- either don't use cygwin or look at the
code in select.cc and suggest a better plan.

cgf

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