Project

General

Profile

Actions

Feature #1530

closed

cgi.max_processes addition

Added by Anonymous almost 14 years ago. Updated over 4 years ago.

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

Description

This patch adds a "cgi.max_processes INT". This limits the number of processes
that can be run via lighttpd. I used this because a small system might run
out of memory.

-- nmav


Files

max_procs.patch (2.65 KB) max_procs.patch Max processes limit patch -- nmav Anonymous, 2008-01-22 08:37

Related issues

Related to Feature #967: request-queue-limit option for mod_fastcgiFixedActions
Related to Feature #2431: mod_cgi process limitFixed2012-08-06Actions
Actions #1

Updated by gstrauss over 5 years ago

  • Assignee deleted (jan)
Actions #2

Updated by gstrauss over 5 years ago

  • Target version deleted (1.5.0)
Actions #3

Updated by gstrauss almost 5 years ago

  • Related to Feature #967: request-queue-limit option for mod_fastcgi added
Actions #4

Updated by gstrauss almost 5 years ago

Actions #5

Updated by gstrauss over 4 years ago

  • Description updated (diff)
  • Status changed from New to Missing Feedback

Since lighttpd 1.4.40, lighttpd no longer blocks if nproc ulimit is reached (after lighttpd starts up). See #2431 for further discussion.

Is this patch still needed? Probably not, as long as you set nproc ulimit to be sufficient number of processes for lighttpd to start up and start any piped loggers. The remaining difference between number of processes at the point and the nproc ulimit should provide similar behavior to your cgi.max_processes patch.

Actions #6

Updated by gstrauss over 4 years ago

  • Status changed from Missing Feedback to Fixed

Marking fixed, as the underlying issue (blocking behavior in CGI) behind this feature request has been fixed since lighttpd 1.4.40.

Actions #7

Updated by gstrauss over 4 years ago

  • Target version set to 1.4.x
Actions

Also available in: Atom