From f2f13898f75900a309240be17b8682b3baf4c331 Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Sun, 7 Oct 2012 23:05:47 +0000 Subject: [PATCH] Adds some clarification to the statement that a default MPM is selected "depending on platform capabilities" git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1395421 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mpm.html.en | 22 ++++++++++++++++++++++ docs/manual/mpm.xml | 24 ++++++++++++++++++++++++ 2 files changed, 46 insertions(+) diff --git a/docs/manual/mpm.html.en b/docs/manual/mpm.html.en index 54738541e2..193dda944c 100644 --- a/docs/manual/mpm.html.en +++ b/docs/manual/mpm.html.en @@ -99,6 +99,28 @@ choice at compile-time.

event, depending on platform capabilities Windowsmpm_winnt + +

Here, 'Unix' is used to mean Unix-like operating systems, such as +Linux, BSD, Solaris, Mac OS X, etc.

+ +

In the case of Unix, the decision as to which MPM is installed is +based on two questions:

+

1. Does the system support threads?

+

2. Does the system support polling?

+ +

If the answer to both questions is 'yes', the default MPM is +event.

+ +

If The answer to #1 is 'yes', but the answer to #2 is 'no', the +default will be worker.

+ +

If the answer to both questions is 'no', then the default MPM will be +prefork.

+ +

In practical terms, this means that the default will almost always be +event, as all modern operating systems support these +two features.

+
top

Building an MPM as a static module

diff --git a/docs/manual/mpm.xml b/docs/manual/mpm.xml index 21c0a18611..0150f3f63c 100644 --- a/docs/manual/mpm.xml +++ b/docs/manual/mpm.xml @@ -89,6 +89,30 @@ choice at compile-time.

event, depending on platform capabilities Windowsmpm_winnt + +

Here, 'Unix' is used to mean Unix-like operating systems, such as +Linux, BSD, Solaris, Mac OS X, etc.

+ +

In the case of Unix, the decision as to which MPM is installed is +based on two questions:

+

1. Does the system support threads?

+

2. Does the system support polling?

+ +

If the answer to both questions is 'yes', the default MPM is +event.

+ +

If The answer to #1 is 'yes', but the answer to #2 is 'no', the +default will be worker.

+ +

If the answer to both questions is 'no', then the default MPM will be +prefork.

+ +

In practical terms, this means that the default will almost always be +event, as all modern operating systems support these +two features.

+
Building an MPM as a static module -- 2.40.0