httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod prefork.xml
Date Sun, 02 Jun 2002 15:28:08 GMT
slive       2002/06/02 08:28:08

  Modified:    docs/manual/mod prefork.xml
  Log:
  Too much garbage in the summary.  Just put there what "Joe Average User" needs
  to know.
  
  Revision  Changes    Path
  1.4       +28 -11    httpd-2.0/docs/manual/mod/prefork.xml
  
  Index: prefork.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/prefork.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -d -b -u -r1.3 -r1.4
  --- prefork.xml	23 May 2002 14:50:12 -0000	1.3
  +++ prefork.xml	2 Jun 2002 15:28:08 -0000	1.4
  @@ -10,11 +10,25 @@
   <identifier>mpm_prefork_module</identifier>
   
   <summary>
  -    <p>This Multi-Processing Module (MPM) implements a
  -    non-threaded, pre-forking web server which handles request in a
  -    manner very similar to the default behavior of Apache 1.3 on
  -    Unix.</p>
  +    <p>This Multi-Processing Module (MPM) implements a non-threaded,
  +    pre-forking web server that handles requests in a manner similar
  +    to Apache 1.3.  It is appropriate for sites that need to avoid
  +    threading for compatibility with non-thread-safe libraries.  It
  +    is also the best MPM for isolating each request, so that a problem
  +    with a single request will not affect any other.</p>
   
  +    <p>This MPM is very self-regulating, so it is rarely necessary to
  +    adjust its configuration directives.  Most important is that
  +    <directive module="mpm_common">MaxClients</directive> be big enough to

  +    handle as many simultaneous requests as you expect to receive, but
  +    small enough to assure that there is enough physical RAM for all
  +    processes.</p>
  +
  +</summary>
  +<seealso><a href="../bind.html">Setting which addresses and
  +    ports Apache uses</a></seealso>
  +
  +<section><title>How it Works</title>
       <p>A single control process is responsible for launching child
       processes which listen for connections and serve them when they
       arrive. Apache always tries to maintain several <em>spare</em>
  @@ -46,17 +60,12 @@
       module="mpm_common">Group</directive> 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
  -    addition, unless <a href="../suexec.html">suexec</a> is used,
  -    these directives also set the privileges which will be inherited
  -    by CGI scripts.</p>
  +    should have as few privileges beyond that as possible.</p>
   
       <p><directive module="mpm_common">MaxRequestsPerChild</directive>
       controls how frequently the server recycles processes by killing
       old ones and launching new ones.</p>
  -</summary>
  -<seealso><a href="../bind.html">Setting which addresses and
  -    ports Apache uses</a></seealso>
  +</section>
   
   <directivesynopsis location="mpm_common">
   <name>CoreDumpDirectory</name>
  @@ -79,6 +88,10 @@
   </directivesynopsis>
   
   <directivesynopsis location="mpm_common">
  +<name>MaxClients</name>
  +</directivesynopsis>
  +
  +<directivesynopsis location="mpm_common">
   <name>MaxRequestsPerChild</name>
   </directivesynopsis>
   
  @@ -108,6 +121,10 @@
   
   <directivesynopsis location="mpm_common">
   <name>User</name>
  +</directivesynopsis>
  +
  +<directivesynopsis location="mpm_common">
  +<name>Group</name>
   </directivesynopsis>
   
   <directivesynopsis>
  
  
  

Mime
View raw message