Project

General

Profile

Actions
Copy link

Bug #2052

closed

Lighttpd install signal handlers too late

Added by pi3orama over 15 years ago. Updated over 1 year ago.

Status:
Fixed
Priority:
Normal
Category:
-
Target version:
-
ASK QUESTIONS IN Forums:
No

Description

lighttpd install signal handlers after it initialize plugins. If user use mod_fastcgi, this arrangement may prevent lighttpd kill forked fcgi workers. For example, in fcgi_spawn_connection(), after the fork(), there's a select() call. If a SIGTERM raises here, lighttpd will be killed, but the forked fcgi worker won't get killed.

Someone report after lighttpd killed, spawned php-cgi still alive:

http://bugs.php.net/bug.php?id=40286

I think this is one of the reasons.

Files

patch (2.62 KB) patch pi3orama, 2009-08-19 05:13
Actions
Copy link
 #1

Updated by pi3orama over 15 years ago

  • Target version set to 1.4.x
Actions
Copy link
 #2

Updated by stbuehler over 15 years ago

  • Missing in 1.5.x set to No

I don't think this is the reason that php-cgi doesn't die; there are other reasons for this (we got reports where the strace even shows the kill, but php just ignores it).

If that really is a problem for you, just don't kill lighty that fast... or use spawn-fcgi.

Actions
Copy link
 #3

Updated by stbuehler over 14 years ago

  • Status changed from New to Wontfix
  • Target version deleted (1.4.x)
Actions
Copy link
 #4

Updated by gstrauss over 1 year ago

  • Status changed from Wontfix to Fixed
  • ASK QUESTIONS IN Forums set to No

lighttpd install signal handlers after it initialize plugins.

Fixed in #2502 in lighttpd 1.4.33 in 2013.

Actions
Copy link

Also available in: Atom