This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: listen/accept/fork behavior problem between cygwin1 1.5.18 and cygwin1.dll 1.5.19
- From: clayne at anodized dot com
- To: cygwin at cygwin dot com
- Date: Wed, 14 Jun 2006 19:30:24 -0700
- Subject: Re: listen/accept/fork behavior problem between cygwin1 1.5.18 and cygwin1.dll 1.5.19
- References: <20060519024910.GA32309@ns1.anodized.com> <20060614204025.GY16683@calimero.vinschen.de>
On Wed, Jun 14, 2006 at 10:40:25PM +0200, Corinna Vinschen wrote:
>
> Thanks very much for your testcase. I applied a patch to Cygwin, please
> give the next developer snapshot from http://cygwin.com/snapshots/ a try.
>
> Corinna
Thank you Corinna. This appears to work much better and expected. BTW: I think
the same issue may also exist for both read() and write() and possibly any other
read, write, send, recv variant when using multiple threads as opposed to single
thread + select(). One thing I notice is that if a read() is in progress and one
is currently sitting in select(), all other read()s in seperate select()s will
then stall if the former read() times out or takes longer than expected.
-cl
--
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/