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/httpd.pid`, the problem is there.
