don't do anything
> under normal circumstances, if they aren't clearly advantageous.
> Anyway, maybe talk a bit more about what front-ends you see this being used
> with and so on and maybe the need will be clearer.
> Thanks.
>
> At 09:04 AM 12/2/2004 +0100, Christer
be missing something. Again, why shouldn't this be the job of
> whatever is running the FastCGI stuff? So what if it's a web frontend? It
> should be able to kill the mother implementation so that it also kills its
> children.
>
> At 08:27 AM 12/2/2004 +0100, Christe
y this patch is needed. It's the FastCGI implementation's job
> to do the right thing and terminate the processes according to some kind of
> strategy. The FCGI processes shouldn't self destruct.
>
> Andi
>
> At 07:11 PM 12/1/2004 +0100, Christer Holgersson wrote
Included is a patch that adds a PHP_FCGI_TIMEOUT that works
somewhat akin to PHP_FCGI_MAX_REQUESTS. With PHP_FCGI_TIMEOUT
set to 300 the whole fcgi process will terminate after 300 sec
with no request to any of the worker children - great for those
seldom used dynamically created fcgi scripts.
Ch
