Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 536 — #562
i
i
i
i
i
i
i
i
The option -a should not be used with Apache 2, as this would cause the
changes to be written directly to /etc/apache2/httpd.conf. Rather,
modules should be activated by means of the entry APACHE_MODULES in
/etc/sysconfig/apache2 as described in Section 22.7.1.
22.7 Configuration
Following the installation of Apache, additional changes are only nec-
essary if you have special needs or preferences. Apache can be config-
ured either with SuSEconfig or by directly editing the file /etc/apache2/
httpd.conf.
22.7.1 Configuration with SuSEconfig
The settings made in /etc/sysconfig/apache2 are applied to the
Apache configuration files by SuSEconfig. The offered configuration op-
tions should be sufficient for most scenarios. Each variable found in the file
is provided with a comment explaining its effect.
Custom Configuration Files
Instead of performing changes directly in the configuration file /etc/
apache2/httpd.conf, you can designate your own configuration file
(such as httpd.conf.local) with the help of the variable APACHE_-
CONF_INCLUDE_FILES. Consequently, the file is interpreted by the main
configuration file. In this way, changes to the configuration are retained
even if the file /etc/apache2/httpd.conf is overwritten during a new
installation.
Modules
Modules installed with YaST can be activated by including the name of the
module in the list specified under the variable APACHE_MODULES. This
variable is defined in the file /etc/sysconfig/apache2.
Flags
APACHE_SERVER_FLAGS can be used to specify flags that activate or deac-
tivate certain sections of the configuration file. If a section in the configura-
tion file is enclosed in
536 22.7. Configuration