Keepalivetimeout; Ifmodule; Mpm Specific Server-Pool Directives - Red Hat ENTERPRISE LINUX 4.5.0 Reference Manual

Table of Contents

Advertisement

Apache Project recommends a high setting, which improves the server's performance.
MaxKeepAliveRequests
situations.
5.7.

KeepAliveTimeout

sets the number of seconds the server waits after a request has been
KeepAliveTimeout
served before it closes the connection. Once the server receives a request, the
directive applies instead. The
5.8.

IfModule

and
<IfModule>
</IfModule>
specified module is loaded. Directives within the
of two conditions. The directives are processed if the module contained within the starting
tag is loaded. Or, if an exclamation point ! appears before the module name, the
<IfModule>
directives are processed only if the module specified in the
For more information about Apache HTTP Server modules, refer to
Modules".

5.9. MPM Specific Server-Pool Directives

As explained in
Section 2.1.2, "Server-Pool Size
characteristics of the server-pool falls to a module group called MPMs under Apache HTTP
Server 2.0. The characteristics of the server-pool differ depending upon which MPM is used. For
this reason, an
IfModule
By default, Apache HTTP Server 2.0 defines the server-pool for both the
MPMs.
The following section list directives found within the MPM-specific server-pool containers.
5.9.1.
StartServers
The
directive sets how many server processes are created upon startup. Since
StartServers
the Web server dynamically kills and creates server processes based on traffic load, it is not
necessary to change this parameter. The Web server is set to start
startup for the
prefork
5.9.2.
MaxRequestsPerChild
MaxRequestsPerChild
before the child dies. The main reason for setting
process induced memory leaks. The default
and for the
4000
worker
5.9.3.
MaxClients
is set to
by default, which should be appropriate for most
100
KeepAliveTimeout
tags create a conditional container which are only activated if the
container is necessary to define the server-pool for the MPM in use.
MPM and
for the
2
worker
sets the total number of requests each child server process serves
MaxRequestsPerChild
MPM is
.
0
directive is set to 15 seconds by default.
container are processed under one
IfModule
<IfModule>
Section 7, "Adding
Regulation", the responsibility for managing
server processes at
8
MPM.
MaxRequestsPerChild
for the
KeepAliveTimeout
Timeout
tag is not loaded.
and
prefork
worker
is to avoid long-lived
MPM is
prefork
165

Advertisement

Table of Contents
loading

Table of Contents