This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: [tolj@wapme-systems.de: Re: Problem with accept?!! (was: Re: apache cygwin package hangs when MaxRequestsPerChild reached!)]
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Mon, 2 Jun 2003 14:36:05 -0400
- Subject: Re: [tolj@wapme-systems.de: Re: Problem with accept?!! (was: Re: apache cygwin package hangs when MaxRequestsPerChild reached!)]
- References: <20030602111825.GH875@cygbert.vinschen.de> <20030602175550.GM875@cygbert.vinschen.de>
- Reply-to: cygwin-developers at cygwin dot com
On Mon, Jun 02, 2003 at 07:55:50PM +0200, Corinna Vinschen wrote:
>On Mon, Jun 02, 2003 at 01:18:25PM +0200, Corinna Vinschen wrote:
>> Duplicated sockets all share the same event handler.
>> [...]
>> As a starting point I'm now throwing some fuel in here: What about
>> running accept and connect in another thread which can be terminated
>> using TerminateThread if a signal arrives?
>
>I've applied a patch which implements blocking accept and connect now
>using threads. All my tests worked (ssh, ftp, telnet rlogin, rsh,
>fake server and client to test interrupting the blocking calls) but
>nevertheless I'd appreciate if somebody takes a heart and gives that
>stuff also a thorough testing.
>
>Chris, could you trigger a new snapshot? I'd like to have Stipe and
>friends testing this with apache.
I've triggered a new snapshot but I noticed that you are using the same
technique that I'm using for pipes which is known to leak memory, if not
resources. I hope the cure here isn't worse than the disease.
cgf