You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by tr...@apache.org on 2009/11/04 20:45:11 UTC
svn commit: r832859 - /httpd/httpd/trunk/docs/manual/programs/configure.xml
Author: trawick
Date: Wed Nov 4 19:45:10 2009
New Revision: 832859
URL: http://svn.apache.org/viewvc?rev=832859&view=rev
Log:
document --enable-mpms-shared
Modified:
httpd/httpd/trunk/docs/manual/programs/configure.xml
Modified: httpd/httpd/trunk/docs/manual/programs/configure.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/programs/configure.xml?rev=832859&r1=832858&r2=832859&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/programs/configure.xml (original)
+++ httpd/httpd/trunk/docs/manual/programs/configure.xml Wed Nov 4 19:45:10 2009
@@ -633,9 +633,49 @@
</dl>
</section>
- <section id="modules"><title>MPMs and third-party modules</title>
- <p>To add the necessary Multi Processing Module and additional third-party
- modules use the following options:</p>
+ <section id="mpms"><title>Multi-Processing Modules</title>
+ <p><a href="../mpm.html">Multi-Processing Modules</a>, or MPMs, implement
+ the basic behavior of the server. A single MPM must be active in order
+ for the server to function. The list of available MPMs appears on the
+ <a href="../mod/">module index page</a>.</p>
+
+ <p>MPMs can be built as DSOs for dynamic loading or statically linked with
+ the server, and are enabled using the following options:</p>
+
+ <dl>
+ <dt><code>--with-mpm=MPM</code></dt>
+ <dd>
+ <p>Choose the default MPM for your server. If MPMs are built as DSO
+ modules (see <code>--enable-mpms-shared</code>), this directive
+ selects the MPM which will be loaded in the default configuration
+ file. Otherwise, this directive selects the only available MPM,
+ which will be statically linked into the server.</p>
+ <p>If this option is omitted, the <a href="../mpm.html#defaults">default
+ MPM</a> for your operating system will be used.</p>
+ </dd>
+
+ <dt><code>--enable-mpms-shared=<var>MPM-LIST</var></code></dt>
+ <dd>
+ <p>Enable a list of MPMs as dynamic shared modules. One of these
+ modules must be loaded dynamically using the
+ <directive module="mod_so">LoadModule</directive> directive.</p>
+ <p><var>MPM-LIST</var> is a space-separated list of MPM names
+ enclosed by quotation marks. For example:</p>
+ <example>
+ --enable-mpms-shared='prefork worker'
+ </example>
+ <p>Additionally you can use the special keyword <code>all</code>,
+ which will select all MPMs which support dynamic loading on the
+ current platform and build them as DSO modules. For example:</p>
+ <example>
+ --enable-mpms-shared=all
+ </example>
+ </dd>
+ </dl>
+ </section>
+
+ <section id="modules"><title>Third-party modules</title>
+ <p>To add additional third-party modules use the following options:</p>
<dl>
<dt><code>--with-module=<var>module-type</var>:<var>module-file</var>[,
@@ -656,13 +696,6 @@
If you want to build a DSO module instead of a statically linked
use <program>apxs</program>.</note>
</dd>
-
- <dt><code>--with-mpm=MPM</code></dt>
- <dd>Choose the process model for your server. You have to select
- exactly one <a href="../mpm.html">Multi-Processing Module</a>.
- Otherwise the <a href="../mpm.html#defaults">default MPM</a> for
- your operating system will be taken. Possible MPMs are
- <module>prefork</module> and <module>worker</module>.</dd>
</dl>
</section>