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

[Christopher Faylor]

On Fri, May 28, 2004 at 07:29:41PM +0200, Alexander Gottwald wrote:
>Caphe Noir wrote:
>>Looks like the "-multiwindow" option is the one causing the listening
>>ports.
>>
>>Something interesting, when running without the "multiwindow" option.
>>I tried to run sawfish (window manager), after which, sawfish is the
>>one that spawns the listening sockets every second just like XWin did.
>
>What happens if you start no windowmanager at all, just on xterm.  Does
>it spawn new connections too?

This isn't just the standard complaint that's due to cygwin's select
implementation opening a dummy port every time it's called is it?

cgf