httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From alex dyas <>
Subject Re: No Effect On Changing Directives
Date Wed, 13 Mar 2002 09:31:10 GMT
I think (and someone correct me if I'm wrong) what happens is that 
apachectl kills the parent httpd daemon, but does nothing about the 
children. It is up to each of the children in turn to kill themselves 
when they see that the parent has died. If one of the children is at 
that point stuck doing something it may hang around longer than you 
expect.  I've seen this quite often.

What I don't understand is why this should affect the daemon if it's 
started again. Ie, if you don't wait for all the children to die, and 
start the damon up again you get these weird situations. Anyone?


Weifeng Wang wrote:
> Thanks.  The httpd.conf I modified is the right one.  But, the "apachectl
> stop" did not really stop the httpd.  Again, thank you very much for your
> reply.
> Weifeng Wang
-= alex dyas - webmaster - twowaytv - uk =-

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message