On Tue, Aug 30, 2005 at 08:24:17AM -0000, [EMAIL PROTECTED] wrote: > Modified: httpd/httpd/trunk/docs/manual/stopping.xml > URL: > http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/stopping.xml?rev=264737&r1=264736&r2=264737&view=diff > ============================================================================== > --- httpd/httpd/trunk/docs/manual/stopping.xml (original) > +++ httpd/httpd/trunk/docs/manual/stopping.xml Tue Aug 30 01:24:14 2005 > @@ -190,13 +190,15 @@ > <p>The <code>WINCH</code> or <code>graceful-stop</code> signal causes > the parent process to <em>advise</em> the children to exit after > their current request (or to exit immediately if they're not > - serving anything). The parent will then remove it's <directive > + serving anything). The parent will then remove its <directive
erk :) > module="mpm_common">PidFile</directive> and cease listening on > all ports. The parent will continue to run, and monitor children > which are handling requests. Once all children have finalised > and exited or the timeout specified by the <directive > module="mpm_common">GracefulShutdownTimeout</directive> has been > - reached, the parent will also exit.</p> > + reached, the parent will also exit. If the timeout is reached, > + any remaining children will be sent the <code>TERM</code> signal > + to force them to exit.</p> This is only the case on prefork, on the threaded MPM's its more complicated that that. The children are told via the pod to exit, but TERM is not sent explicitly, instead the children will get sent HUP due to parent exit. This has all sorts of consequences, the most annoying of which is that both "stop" and "graceful-stop" actually won't kill CGI processes when using a threaded MPM/cgid. -- Colm MacCárthaigh Public Key: [EMAIL PROTECTED]
