You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ke...@apache.org on 2003/03/30 05:14:17 UTC
cvs commit: httpd-2.0/docs/manual/mod worker.xml worker.html.en
kess 2003/03/29 19:14:17
Modified: docs/manual/mod Tag: APACHE_2_0_BRANCH worker.xml
worker.html.en
Log:
some nits
Revision Changes Path
No revision
No revision
1.8.2.2 +7 -7 httpd-2.0/docs/manual/mod/worker.xml
Index: worker.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/worker.xml,v
retrieving revision 1.8.2.1
retrieving revision 1.8.2.2
diff -u -r1.8.2.1 -r1.8.2.2
--- worker.xml 22 Dec 2002 23:35:33 -0000 1.8.2.1
+++ worker.xml 30 Mar 2003 03:14:17 -0000 1.8.2.2
@@ -14,12 +14,12 @@
multi-process multi-threaded server. By using threads to serve
requests, it is able to serve a large number of requests with
less system resources than a process-based server. Yet it
- retains much of the stability of a process-based server by
+ retains much of the stability of a process-based server by
keeping multiple processes available, each with many threads.</p>
<p>The most important directives used to control this MPM are
<directive module="mpm_common">ThreadsPerChild</directive>, which
- controls the number of threads deployed by each child process and
+ controls the number of threads deployed by each child process, and
<directive module="mpm_common">MaxClients</directive>, which
controls the maximum total number of threads that may be
launched.</p>
@@ -75,9 +75,9 @@
ServerLimit 16
</example>
- <p>While the parent process is usually started as root under Unix
- in order to bind to port 80, the child processes and threads are
- launched by Apache as a less-privileged user. The <directive
+ <p>While the parent process is usually started as <code>root</code>
+ under Unix in order to bind to port 80, the child processes and threads
+ are launched by Apache as a less-privileged user. The <directive
module="mpm_common">User</directive> and <directive
module="mpm_common">Group</directive> directives are used to set
the privileges of the Apache child processes. The child processes
@@ -91,7 +91,7 @@
controls how frequently the server recycles processes by killing
old ones and launching new ones.</p>
</section>
-
+
<directivesynopsis location="mpm_common"><name>AcceptMutex</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>CoreDumpDirectory</name>
@@ -131,4 +131,4 @@
<directivesynopsis location="mpm_common"><name>User</name>
</directivesynopsis>
-</modulesynopsis>
+</modulesynopsis>
\ No newline at end of file
1.15.2.3 +5 -5 httpd-2.0/docs/manual/mod/worker.html.en
Index: worker.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/worker.html.en,v
retrieving revision 1.15.2.2
retrieving revision 1.15.2.3
diff -u -r1.15.2.2 -r1.15.2.3
--- worker.html.en 23 Dec 2002 00:03:54 -0000 1.15.2.2
+++ worker.html.en 30 Mar 2003 03:14:17 -0000 1.15.2.3
@@ -31,12 +31,12 @@
multi-process multi-threaded server. By using threads to serve
requests, it is able to serve a large number of requests with
less system resources than a process-based server. Yet it
- retains much of the stability of a process-based server by
+ retains much of the stability of a process-based server by
keeping multiple processes available, each with many threads.</p>
<p>The most important directives used to control this MPM are
<code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code>, which
- controls the number of threads deployed by each child process and
+ controls the number of threads deployed by each child process, and
<code class="directive"><a href="../mod/mpm_common.html#maxclients">MaxClients</a></code>, which
controls the maximum total number of threads that may be
launched.</p>
@@ -116,9 +116,9 @@
ServerLimit 16
</code></p></div>
- <p>While the parent process is usually started as root under Unix
- in order to bind to port 80, the child processes and threads are
- launched by Apache as a less-privileged user. The <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> and <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code> directives are used to set
+ <p>While the parent process is usually started as <code>root</code>
+ under Unix in order to bind to port 80, the child processes and threads
+ are launched by Apache as a less-privileged user. The <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> and <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code> directives are used to set
the privileges of the Apache child processes. The child processes
must be able to read all the content that will be served, but
should have as few privileges beyond that as possible. In