file defined by the <code class="directive"><a href="#lockfile">LockFile</a></code> directive.</dd>
<dt><code>fcntl</code></dt>
- <dd>uses the <code>fnctl(2)</code> system call to lock the
+ <dd>uses the <code>fcntl(2)</code> system call to lock the
file defined by the <code class="directive"><a href="#lockfile">LockFile</a></code> directive.</dd>
<dt><code>posixsem</code></dt>
</table>
<p>The <code class="directive">Group</code> directive sets the group under
which the server will answer requests. In order to use this
- directive, the server must be run initially as root. If you start the
- server as a non-root user, it will fail to change to the specified
- group, and will instead continue to run as the group of the original
- user. <var>Unix-group</var> is one of:</p>
+ directive, the server must be run initially as <code>root</code>. If
+ you start the server as a non-root user, it will fail to change to the
+ specified group, and will instead continue to run as the group of the
+ original user. <var>Unix-group</var> is one of:</p>
<dl>
<dt>A group name</dt>
of the main server process is automatically appended to the
filename.</p>
- <div class="warning"><h3>Security:</h3>
+ <div class="warning"><h3>Security</h3>
<p>It is best to <em>avoid</em> putting this file in a world writable
directory such as <code>/var/tmp</code> because someone could create
a denial of service attack and prevent the server from starting by
<p>For non-threaded servers (<em>i.e.</em>, <code class="module"><a href="../mod/prefork.html">prefork</a></code>),
<code class="directive">MaxClients</code> translates into the maximum
number of child processes that will be launched to serve requests.
- The default value is 256; to increase it, you must also raise
+ The default value is <code>256</code>; to increase it, you must also raise
<code class="directive"><a href="#serverlimit">ServerLimit</a></code>.</p>
<p>For threaded and hybrid servers (<em>e.g.</em> <code class="module"><a href="../mod/beos.html">beos</a></code>
process will die. If <code class="directive">MaxRequestsPerChild</code> is
<code>0</code>, then the process will never expire.</p>
- <div class="note"><h3>Different default values:</h3>
+ <div class="note"><h3>Different default values</h3>
<p>The default value for <code class="module"><a href="../mod/mpm_netware.html">mpm_netware</a></code> and
<code class="module"><a href="../mod/mpm_winnt.html">mpm_winnt</a></code> is <code>0</code>.</p>
</div>
the number of processes when the server load reduces.</li>
</ul>
- <div class="note"><h3>Note:</h3>
+ <div class="note"><h3>Note</h3>
<p>For <code class="directive"><a href="../mod/core.html#keepalive">KeepAlive</a></code> requests, only
the first request is counted towards this limit. In effect, it
changes the behavior to limit the number of <em>connections</em> per
SIGHUP (kill -1) signal to the process id listed in the
<code class="directive">PidFile</code>.</p>
- <p>The PidFile is subject to the same warnings about log file
- placement and <a href="../misc/security_tips.html#serverroot">security</a>.</p>
+ <p>The <code class="directive">PidFile</code> is subject to the same
+ warnings about log file placement and <a href="../misc/security_tips.html#serverroot">security</a>.</p>
<div class="note"><h3>Note</h3>
- As of Apache 2 it is recommended to use only the <a href="../programs/apachectl.html">apachectl</a> script for
- (re-)starting or stopping the server.
+ <p>As of Apache 2 it is recommended to use only the <a href="../programs/apachectl.html">apachectl</a> script for
+ (re-)starting or stopping the server.</p>
</div>
</div>
</table>
<p>For the <code class="module"><a href="../mod/prefork.html">prefork</a></code> MPM, this directive sets the
maximum configured value for <code class="directive"><a href="#maxclients">MaxClients</a></code> for the lifetime of the
- Apache process. For the worker MPM, this directive in combination
- with <code class="directive"><a href="#threadlimit">ThreadLimit</a></code> sets
+ Apache process. For the <code class="module"><a href="../mod/worker.html">worker</a></code> MPM, this directive
+ in combination with <code class="directive"><a href="#threadlimit">ThreadLimit</a></code> sets
the maximum configured value for <code class="directive"><a href="#maxclients">MaxClients</a></code> for the lifetime of the
Apache process. Any attempts to change this directive during a
restart will be ignored, but <code class="directive"><a href="#maxclients">MaxClients</a></code> can be modified during
>LockFile</directive> directive.</dd>
<dt><code>fcntl</code></dt>
- <dd>uses the <code>fnctl(2)</code> system call to lock the
+ <dd>uses the <code>fcntl(2)</code> system call to lock the
file defined by the <directive module="mpm_common"
>LockFile</directive> directive.</dd>
<usage>
<p>The <directive>Group</directive> directive sets the group under
which the server will answer requests. In order to use this
- directive, the server must be run initially as root. If you start the
- server as a non-root user, it will fail to change to the specified
- group, and will instead continue to run as the group of the original
- user. <var>Unix-group</var> is one of:</p>
+ directive, the server must be run initially as <code>root</code>. If
+ you start the server as a non-root user, it will fail to change to the
+ specified group, and will instead continue to run as the group of the
+ original user. <var>Unix-group</var> is one of:</p>
<dl>
<dt>A group name</dt>
SIGHUP (kill -1) signal to the process id listed in the
<directive>PidFile</directive>.</p>
- <p>The PidFile is subject to the same warnings about log file
- placement and <a
+ <p>The <directive>PidFile</directive> is subject to the same
+ warnings about log file placement and <a
href="../misc/security_tips.html#serverroot">security</a>.</p>
<note><title>Note</title>
- As of Apache 2 it is recommended to use only the <a
+ <p>As of Apache 2 it is recommended to use only the <a
href="../programs/apachectl.html">apachectl</a> script for
- (re-)starting or stopping the server.
+ (re-)starting or stopping the server.</p>
</note>
</usage>
</directivesynopsis>
of the main server process is automatically appended to the
filename.</p>
- <note type="warning"><title>Security:</title>
+ <note type="warning"><title>Security</title>
<p>It is best to <em>avoid</em> putting this file in a world writable
directory such as <code>/var/tmp</code> because someone could create
a denial of service attack and prevent the server from starting by
<p>For non-threaded servers (<em>i.e.</em>, <module>prefork</module>),
<directive>MaxClients</directive> translates into the maximum
number of child processes that will be launched to serve requests.
- The default value is 256; to increase it, you must also raise
+ The default value is <code>256</code>; to increase it, you must also raise
<directive module="mpm_common">ServerLimit</directive>.</p>
<p>For threaded and hybrid servers (<em>e.g.</em> <module>beos</module>
process will die. If <directive>MaxRequestsPerChild</directive> is
<code>0</code>, then the process will never expire.</p>
- <note><title>Different default values:</title>
+ <note><title>Different default values</title>
<p>The default value for <module>mpm_netware</module> and
<module>mpm_winnt</module> is <code>0</code>.</p>
</note>
the number of processes when the server load reduces.</li>
</ul>
- <note><title>Note:</title>
+ <note><title>Note</title>
<p>For <directive module="core">KeepAlive</directive> requests, only
the first request is counted towards this limit. In effect, it
changes the behavior to limit the number of <em>connections</em> per
<p>For the <module>prefork</module> MPM, this directive sets the
maximum configured value for <directive
module="mpm_common">MaxClients</directive> for the lifetime of the
- Apache process. For the worker MPM, this directive in combination
- with <directive module="mpm_common">ThreadLimit</directive> sets
+ Apache process. For the <module>worker</module> MPM, this directive
+ in combination with <directive
+ module="mpm_common">ThreadLimit</directive> sets
the maximum configured value for <directive
module="mpm_common">MaxClients</directive> for the lifetime of the
Apache process. Any attempts to change this directive during a