[patch] fix for rlimit documentation

[David Harris <dh...@drh.net>]

The current documentation on the Rlimit{CPU,MEM,Nproc} directives is
misleading, I think.

They all say:

> Takes 1 or 2 parameters. The first parameter sets the soft
> resource limit for all processes and the second parameter
> sets the maximum resource limit. Either parameter can be
> a number, or max to indicate to the server that the limit
> should be set to the maximum allowed by the operating system
> configuration. Raising the maximum resource limit requires that
> the server is running as root, or in the initial startup phase.

The documentation uses the wording "for all processes" which leads one to
believe that the limit applies to all of the Apache children processes.
However, this is not the case. The resource limits are applied in
ap_call_exec() which is only called by mod_cgi and mod_include. I've appended a
patch which specifics where the limit applies with a little more detail.

 - David Harris
   Principal Engineer, DRH Internet Services


--- htdocs/manual/mod/core.html.orig    Sun Aug 15 00:38:20 1999
+++ htdocs/manual/mod/core.html Sun Aug 15 00:47:29 1999
@@ -2457,6 +2457,11 @@
 configuration. Raising the maximum resource limit requires that the server
 is running as root, or in the initial startup phase.<P>

+This applies to processes forked off from Apache children servicing requests,
+not the Apache children themselves. This includes CGI scripts and SSI
+exec commands, but not any processes forked off from the Apache parent
+such as piped logs.<P>
+
 CPU resource limits are expressed in seconds per process.<P>

 See also <A HREF="#rlimitmem">RLimitMEM</A> or
@@ -2495,6 +2500,11 @@
 configuration. Raising the maximum resource limit requires that the
 server is running as root, or in the initial startup phase.<P>

+This applies to processes forked off from Apache children servicing requests,
+not the Apache children themselves. This includes CGI scripts and SSI
+exec commands, but not any processes forked off from the Apache parent
+such as piped logs.<P>
+
 Memory resource limits are expressed in bytes per process.<P>

 See also <A HREF="#rlimitcpu">RLimitCPU</A> or
@@ -2532,6 +2542,11 @@
 that the limit should be set to the maximum allowed by the operating system
 configuration. Raising the maximum resource limit requires that the server
 is running as root, or in the initial startup phase.<P>
+
+This applies to processes forked off from Apache children servicing requests,
+not the Apache children themselves. This includes CGI scripts and SSI
+exec commands, but not any processes forked off from the Apache parent
+such as piped logs.<P>

 Process limits control the number of processes per user.<P>