Doug MacEachern wrote:
> > 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.
Aha, I just duplicated what you are talking about. Apparently something regressed
before I committed. I had this working so that the kill -TERM `cat logs/httpd.pid`
worked (sometimes spitting out some "SIGTERM" messages), and never left kids
around.
The problem you are seeing is one that I encountered but had fixed. I'll take a
look at my development machine when I get home tomorrow and see what I missed.
You are right, this is more than annoying.
--
Paul J. Reder
-----------------------------------------------------------
"The strength of the Constitution lies entirely in the determination of each
citizen to defend it. Only if every single citizen feels duty bound to do
his share in this defense are the constitutional rights secure."
-- Albert Einstein
