Project

General

Profile

Bug #1856

Lighttpd always sends SIGTERM to FCGI-Processes

Added by medic over 10 years ago. Updated over 10 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
mod_fastcgi
Target version:
Start date:
2008-12-23
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

Not depending on how lighttpd is signaled, it is always sending SIGTERM.
This is a big tragedy, because if one issues "RELOAD", the fcgi-handlers are killed (SIGTERM), but not respawned anymore.

Trapping SIGTERM and not killing the FCGI-Handlers isn't really an option, because one will detach FCGI processes from the lighttpd webserver, so an automated webserver-restart in case of error will not terminate the fcgi-children.

History

#1

Updated by medic over 10 years ago

  • Target version changed from 1.4.19 to 1.4.21
#2

Updated by icy over 10 years ago

  • Target version changed from 1.4.21 to 1.4.22
#3

Updated by stbuehler over 10 years ago

  • Status changed from New to Invalid

See "kill-signal" in Docs:ModFastCGI; and lighty only forwards SIGHUP to all procs in the same process group (as SIGHUP).

Also available in: Atom