[FASTCGI] Terminated

double ninive at gmx.at
Mon Mar 16 13:25:15 EDT 2009

Jay Sprenkle schrieb:
> On Fri, Mar 13, 2009 at 10:48 AM, double <ninive at gmx.at 
> <mailto:ninive at gmx.at>> wrote:
>     Should the application - after receiving a SIGTERM - finish the
>     current
>     request?
> I believe that is best. It's more friendly toward the user if they get 
> an explanation of a problem.

Hello Jay,

Thank you very much for your answer.
Does mod_fastcgi not distinguish between
* SIGTERM - terminate as quick as possible (e.g. webserver shutdown)
* SIGUSR1 - finish current request and shut down

In the apache error log there are a lot of
    [Mon Mar 16 17:21:16 2009] [warn] FastCGI: scheduled the start of 
the last
    (dynamic) server "/path" process: reached dynamicMaxClassProcs (10)
The application receives a SIGTERM in that case, but should receive a
SIGUSR1, shouldn't it?

Thank you very much

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.pins.net/mailman/private.cgi/fastcgi-developers/attachments/20090316/46cef420/attachment.html>

More information about the FastCGI-developers mailing list