Add a note in ThreadsPerChild about the relationship with ThreadsLimit.

+ add a missing link

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1838958 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mpm_common.xml b/docs/manual/mod/mpm_common.xml
index d1e09eeed5129a3a81747c3a497db9b10240eec1..6508ca7e494260edcd3719b0c2987daa4e657a19 100644 (file)
--- a/docs/manual/mod/mpm_common.xml
+++ b/docs/manual/mod/mpm_common.xml
@@ -270,7 +270,7 @@ in *BSDs.</compatibility>
     <p>A <var>ratio</var> between the number of (online) CPU cores and the
     number of listeners' buckets can be used to make Apache HTTP Server create
     <code>num_cpu_cores / ratio</code> listening buckets, each containing its
-    own <directive>Listen</directive>-ing socket(s) on the same port(s), and
+    own <directive module="mpm_common">Listen</directive>-ing socket(s) on the same port(s), and
     then make each child handle a single bucket (with round-robin distribution
     of the buckets at children creation time).</p>
 
@@ -812,6 +812,12 @@ per child process</description>
     <p>The default value for <directive>ThreadsPerChild</directive> is
     <code>64</code> when used with <module>mpm_winnt</module> and
     <code>25</code> when used with the others.</p>
+    
+    <p>The value of <directive>ThreadsPerChild</directive> can not exceed the
+    value of <directive module="mpm_common">ThreadsLimit</directive>. If a
+    higher value is configured, it will be automatically reduced at start-up
+    and a warning will be logged. The relationship between these 2 directives
+    is explained in <directive module="mpm_common">ThreadsLimit</directive>.</p>
 </usage>
 </directivesynopsis>