httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject Re: Apache 2.0.17 tarballs up
Date Tue, 17 Apr 2001 21:12:08 GMT
On Tue, 17 Apr 2001, Doug MacEachern wrote:

> On Tue, 17 Apr 2001, Paul J. Reder wrote:
> > I saw some cases where the kids were slow to shut down during testing.
> > What I found was that since the kids are not shutdown directly via
> > signal, but indirectly via flag, some of the kids took a little longer
> > than before. The kids a now allowed to finish their processing. This is
> > the nature of the fix to avoid the deadlock that occurred when they were
> > shutdown immediately.
> >
> > This is why I shifted the point in the switch statement to delay the time
> > period before Apache complained and SIGTERMed (or SIGKILLed) again.
> >
> > In my tests, the kids eventually went down. The messages and extra kills
> > were mostly just an annoyance.
> much more than annoyance, we're talking 10+ seconds for the parent to
> finally send a SIGKILL to the children, then all the children hang around
> as defunct processes for a while longer.  this happens with both prefork
> and threaded.  i'm testing with vanilla builds, no extra modules added,
> default configuration other than changing the port.  start the server, do
> not even make a single request (the kids are not processing anything), try
> to kill `cat logs/`, the problem is there.

Looking through the code, we are doing graceful shutdowns in all cases on
the prefork MPM.  That is incorrect.  SIGHUP should be a graceless


Ryan Bloom               
406 29th St.
San Francisco, CA 94131

View raw message