From: Jeff Trawick <trawick@apache.org>
Date: Wed, 4 Nov 2009 19:45:10 +0000 (+0000)
Subject: document --enable-mpms-shared
X-Git-Tag: 2.3.3~52
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d75bace7af32ae59bb7b61a9ec4bedd0b9e5315d;p=apache

document --enable-mpms-shared


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@832859 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/programs/configure.xml b/docs/manual/programs/configure.xml
index 6058142689..3f2c8cd28c 100644
--- a/docs/manual/programs/configure.xml
+++ b/docs/manual/programs/configure.xml
@@ -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>