worker.html revision 5110ced9e3ae72d8eb8e416fdca22ae3ce0fae78
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Apache MPM worker</title>
</head>
<!-- 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>
rel="Help"><strong>Status:</strong></a> MPM<br />
<a href="module-dict.html#SourceFile"
<a href="module-dict.html#ModuleIdentifier"
rel="Help"><strong>Module Identifier:</strong></a>
mpm_worker_module</p>
<h2>Summary</h2>
<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 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>
<p><code>MaxRequestsPerChild</code> controls how frequently the
server recycles processes by killing old ones and launching new
ones.</p>
ports Apache uses</a>.</p>
<h2>Directives</h2>
<ul>
<li><a
<li><a
<li><a
<li><a
<li><a
<li><a
<li><a
<li><a
<li><a
<li><a
<li><a
</ul>
<!--#include virtual="footer.html" -->
</body>
</html>