Finally, it is useful to know that the Apache HTTP Server has a testing mode to check for configuration
errors. To use access it, type the following command:
apachectl configtest
22.2.2.1. Global Environment Configuration
The global environment section of the configuration file contains directives which affect the overall
operation of the Apache HTTP Server, such as the number of concurrent requests it can handle and
the locations of the various files. This section requires a large number of changes and should be
based on the Apache HTTP Server 2.0 configuration file, while migrating the old settings into it.
22.2.2.1.1. Interface and Port Binding
The BindAddress and Port directives no longer exist; their functionality is now provided by a more
flexible Listen directive.
If Port 80 was set in the 1.3 version configuration file, change it to Listen 80 in the 2.0
configuration file. If Port was set to some value other than 80, then append the port number to the
contents of the ServerName directive.
For example, the following is a sample Apache HTTP Server 1.3 directive:
Port 123 ServerName www.example.com
To migrate this setting to Apache HTTP Server 2.0, use the following structure:
Listen 123 ServerName www.example.com:123
For more on this topic, refer to the following documentation on the Apache Software Foundation's
website:
•
http://httpd.apache.org/docs-2.0/mod/mpm_common.html#listen
•
http://httpd.apache.org/docs-2.0/mod/core.html#servername
22.2.2.1.2. Server-Pool Size Regulation
When the Apache HTTP Server accepts requests, it dispatches child processes or threads to handle
them. This group of child processes or threads is known as a server-pool. Under Apache HTTP Server
2.0, the responsibility for creating and maintaining these server-pools has been abstracted to a group
of modules called Multi-Processing Modules (MPMs). Unlike other modules, only one module from
the MPM group can be loaded by the Apache HTTP Server. There are three MPM modules that ship
with 2.0: prefork, worker, and perchild. Currently only the prefork and worker MPMs are
available, although the perchild MPM may be available at a later date.
The original Apache HTTP Server 1.3 behavior has been moved into the prefork MPM. The
prefork MPM accepts the same directives as Apache HTTP Server 1.3, so the following directives
may be migrated directly:
• StartServers
Migrating Apache HTTP Server 1.3 Configuration Files to 2.0
307
Need help?
Do you have a question about the ENTERPRISE LINUX 5 - DEPLOYMENT and is the answer not in the manual?
Questions and answers