Project

General

Profile

Actions
Copy link

Bug #127

closed

fastcgi processes aren't cleaned upon sigkill

Added by Anonymous over 19 years ago. Updated about 16 years ago.

Status:
Invalid
Priority:
High
Category:
mod_fastcgi
Target version:
1.4.9
ASK QUESTIONS IN Forums:

Description

expected behavior:

in lighttpd 1.3.13, when start-stop-daemon is used to stop the lighttpd daemon, all fcgi processes spawned by the configfile method (internal spawning) are also closed as well.

current behavior:

in svn 12/05/2005 lighttpd, when start-stop-daemon is used to stop the lighttpd daemon, all internally spawned fcgi processes are left alive, without SIGKILL or other sent to them to ask them to shut down.

result:

in machines with limited memory, race condition ensues if fastcgi processes are assumed to be garbage collected and they are not, especially php-fastcgi processes that are allowed 16M of memory each.

-- infowolfe

Actions
Copy link
 #1

Updated by jan over 19 years ago

  • Status changed from New to Assigned
Actions
Copy link
 #2

Updated by jan over 19 years ago

  • Status changed from Assigned to Fixed
  • Resolution set to invalid

KILL is KILL, it can't be handled. Use TERM to terminate the process the nice way.

Actions
Copy link
 #3

Updated by stbuehler about 16 years ago

  • Status changed from Fixed to Invalid
Actions
Copy link

Also available in: Atom