httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Orton <jor...@redhat.com>
Subject Re: Flushing lingering CGI processes
Date Thu, 31 Mar 2005 09:05:43 GMT
On Wed, Mar 30, 2005 at 11:02:05PM +0100, Nick wrote:
> I understand that if a CGI process is launched then gets stuck, if the 
> CGI process keeps quiet, the apache server will not 'know' the http 
> connection has broken so will not 'know' to kill the CGI process. The 
> stuck CGI process and the accompanying apache process will then 
> needlessly use system resources indefinately.
> 
> In a worst case scenario, the stuck CGI process will lock some server 
> resource possibly causing many other CGI processes to get stuck, 
> bringing the server down. (I attribute a recent crash to this).
> 
> A great solution for administrators would be to set a timer. If the CGI 
> program hasn't given any output for the given time, the CGI process is 
> killed.

That does happen already: if any CGI script does not output anything for
the period specified by the Timeout directive, it will be killed.  I
think it would be useful to make this separately configurable from the
network I/O timeout.

joe

Mime
View raw message