httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Orton <jor...@redhat.com>
Subject Re: cgi: KILL_AFTER_TIMEOUT vs KILL_ALWAYS
Date Wed, 25 Oct 2006 11:14:49 GMT
On Wed, Oct 25, 2006 at 08:17:22AM +0200, Plüm, Rüdiger, VF EITO wrote:
> > > I believe that the parent process, which is supposed to have a 7 
> > > second space between its own SIGTERM and SIGKILL, is getting the 
> > > SIGKILL before it has slept for 3 seconds *and* sent the final 
> > > SIGKILL to the child CGIs.  This has the potential to leave broken 
> > > child processes behind.
> > 
> > "apachectl stop" never SIGKILLs the parent though, are you using init 
> > scripts for this really?  We had exactly that problem in the
> 
> But the parent httpd process sents SIGKILL to its child processes after a
> timeout, correct? And the cgi's are childs of the httpd childs.

Yes, but Paul was writing about the *parent* getting SIGKILLed before it 
gets a chance to itself SIGKILL any errant CGI scripts.  That won't 
happen with apachectl; but init scripts are indeed written to do a 
"SIGTERM, wait, SIGKILL" on the parent.

joe

Mime
View raw message