httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-2.0/docs/manual/mod worker.html
Date Mon, 19 Nov 2001 18:15:26 GMT
trawick     01/11/19 10:15:26

  Modified:    .        STATUS
  Added:       docs/manual/mod worker.html
  use the old threaded.html contents for worker MPM docs (not carefully
  examined, but there isn't much there that could be wrong)
  Revision  Changes    Path
  1.339     +1 -3      httpd-2.0/STATUS
  Index: STATUS
  RCS file: /home/cvs/httpd-2.0/STATUS,v
  retrieving revision 1.338
  retrieving revision 1.339
  diff -u -r1.338 -r1.339
  --- STATUS	2001/11/19 18:07:27	1.338
  +++ STATUS	2001/11/19 18:15:26	1.339
  @@ -1,5 +1,5 @@
   APACHE 2.0 STATUS:						-*-text-*-
  -Last modified at [$Date: 2001/11/19 18:07:27 $]
  +Last modified at [$Date: 2001/11/19 18:15:26 $]
  @@ -318,8 +318,6 @@
         +1:   Justin, Jeff, Ian
         -0:   Aaron (premature decision, needs more discussion)
         -0:   Cliff (I think the default config should be the safest possible)
  -    * The worker MPM needs some doc.
   PRs that have been suspended forever waiting for someone to
   put them into 'the next release':
  1.1                  httpd-2.0/docs/manual/mod/worker.html
  Index: worker.html
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  <html xmlns="">
      <meta name="generator" content="HTML Tidy, see" />
      <title>Apache MPM worker</title>
    <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
    <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
    vlink="#000080" alink="#FF0000">
      <!--#include virtual="header.html" -->
      <h1 align="CENTER">Multi-Processing Module worker</h1>
      <p>This Multi-Processing Module implements a hybrid
      multi-threaded multi-process web server.</p>
      <p><a href="module-dict.html#Status"
      rel="Help"><strong>Status:</strong></a> MPM<br />
       <a href="module-dict.html#SourceFile"
      rel="Help"><strong>Source File:</strong></a> worker.c<br />
       <a href="module-dict.html#ModuleIdentifier"
      rel="Help"><strong>Module Identifier:</strong></a>
      <p>This Multi-Processing Module (MPM) is the default for most
      unix-like operating systems. It implements a hybrid
      multi-process multi-threaded server. Each process has a fixed
      number of threads. The server adjusts to handle load by
      increasing or decreasing the number of processes.</p>
      <p>A single control process is responsible for launching child
      processes. Each child process creates a fixed number of threads
      as specified in the <code>ThreadsPerChild</code> directive. The
      individual threads then listen for connections and serve them
      when they arrive.</p>
      <p>Apache always tries to maintain a pool of <em>spare</em> or
      idle server threads, which stand ready to serve incoming
      requests. In this way, clients do not need to wait for a new
      threads or processes to be created before their requests can be
      served. Apache assesses the total number of idle threads in all
      processes, and forks or kills processes to keep this number
      within the boundaries specified by <code>MinSpareThreads</code>
      and <code>MaxSpareThreads</code>. Since this process is very
      self-regulating, it is rarely necessary to modify these
      directives from their default values. The maximum number of
      clients that may be served simultaneously is determined by
      multiplying the maximum number of server processes that will be
      created (<code>MaxClients</code>) by the number of threads
      created in each process (<code>ThreadsPerChild</code>).</p>
      <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>User</code> and <code>Group</code> directives are used
      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>
      <p><code>MaxRequestsPerChild</code> controls how frequently the
      server recycles processes by killing old ones and launching new
      <p>See also: <a href="../bind.html">Setting which addresses and
      ports Apache uses</a>.</p>
        <li><a href="mpm_common.html#group">Group</a></li>
        <li><a href="mpm_common.html#pidfile">PidFile</a></li>
        <li><a href="mpm_common.html#listen">Listen</a></li>
        <li><a href="mpm_common.html#lockfile">LockFile</a></li>
        <li><a href="mpm_common.html#maxclients">MaxClients</a></li>
        <li><a href="mpm_common.html#user">User</a></li>
      <!--#include virtual="footer.html" -->

View raw message