This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem with accept?!! (was: Re: apache cygwin package hangs when MaxRequestsPerChild reached!)

On Sun, Jun 01, 2003 at 04:17:06PM -0700, Christopher B. Liebman wrote:
> Ok, after some investigation I am starting to think that the issue is with
> the behavior of accept().  When the apache main forks off its pool of worker
> procs, each one calls accept() on the socket file descriptor.  What I have
> found is that when the first process in the pool exits (usually due to the
> max requests being reached) ***none*** of the other pool process return from
> accept() when the next request comes in on the socket.  If I kill off the
> current pool procs the *first* new one will respond to requests untill the
> max is recieved again then as before, non of the other pool procs return
> from accept.  Any ideas on how to deal with this?

I've just applied a patch to Cygwin which hopefully solves that problem.
Please try out the next developers snapshot.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                      
Red Hat, Inc.

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]