Operation Manual

IMPORTANT: Reload or Restart Apache After Conguration Changes
Most conguration changes require a reload (some also a restart) of Apache
to take effect. Manually reload Apache with rcapache2 reload or use one
of the restart options as described in Section 30.3, “Starting and Stopping
Apache” (page 508).
If you congure Apache with YaST, this can be taken care of automatically if
you set HTTP Service to Enabled as described in Section 30.2.3.2, “HTTP Server
Conguration” (page 506).
30.2.1 Apache Conguration Files
This section gives an overview of the Apache conguration les. If you decide to use
YaST for conguration, you will not need to touch these les—however, the information
might be useful for you if you want to switch to manual conguration later on.
Apache conguration les can be found in two different locations:
•
/etc/sysconfig/apache2 (page 494)
•
/etc/apache2/ (page 494)
30.2.1.1 /etc/syscong/apache2
/etc/sysconfig/apache2 controls some global settings of Apache, like modules
to load, additional conguration les to include, ags with which the server should be
started, and ags that should be added to the command line. Every conguration option
in this le is extensively documented and therefore not mentioned here. For a general-
purpose Web server, the settings in /etc/sysconfig/apache2 should be sufcient
for any conguration needs.
30.2.1.2 /etc/apache2/
/etc/apache2/ hosts all conguration les for Apache. In the following, the purpose
of each le is explained. Each le includes several conguration options (also referred
494 Reference