You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2004/04/17 17:54:28 UTC
DO NOT REPLY [Bug 28449] New: -
RLimitNPROC does not seem to work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28449>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28449
RLimitNPROC does not seem to work
Summary: RLimitNPROC does not seem to work
Product: Apache httpd-2.0
Version: 2.0.49
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Major
Priority: Other
Component: Core
AssignedTo: bugs@httpd.apache.org
ReportedBy: floeff@arcor.de
(I consider this one critical as it can easily bog down a server.)
I run 2.0.49 in Linux 2.4.25. In order to protect from too much memory
allocation for CGI scripts, in set in my httpd.conf
RLimitCPU 6
RLimitNPROC 4
However, this does not seem to work. I invoke my PHP as CGI by using the
binfmt-misc package. .php files are treated like normal CGI scripts. If I load a
simple <? phpinfo(); ?> script and open it 20 time simultaneously, it can crash
my server and get as high as load 60 (!). A lot of php instances are started and
kept open for ages.
Shouldn't the above settings limit that?
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org