Appendix F: LVS Clusters and the Apache Configuration File

Overview

You will use either IP-based or name-based VirtualHost containers in your Apache configuration file to override the general options set at the top of the file when configuring Apache to run on a real server in an LVS cluster. The IP-based or name-based virtual host containers select the proper directory for web files and CGI scripts^[1] for each web host that the real server needs to offer to client computers. We'll discuss when and how to use these two types of Apache virtual hosts later in this appendix, but first let's look at some of the general options you can set in the Apache configuration that will enable the Apache daemon to work properly on an LVS real server.

You should check these general settings, as discussed in the following sections:

• ServerName

• DocumentRoot

• BindAddress (only for Apache versions prior to 2.0)

• Port (only for Apache versions prior to 2.0)

• Listen (replacement for BindAddress and Port)

^[1]This recipe does not discuss CGI scripting. You will need to look at the general configuration file ScriptAlias directive in addition to the general directives mentioned here if you are working with CGI scripts.