Installing, Activating, And Configuring Modules - Novell LINUX ENTERPRISE SERVER 10 SP2 - INSTALLATION AND ADMINISTRATION Installation Manual

server-status and full-server-status
Dumps a short or full status screen, respectively. Requires either lynx or w3m in-
stalled as well as the module mod_status enabled. In addition to that, status must
be added to APACHE_SERVER_FLAGS in the file /etc/sysconfig/apache2.
TIP: Additional Flags
If you specify additional flags to the rcapache2, these are passed through to
the Web server.
40.4 Installing, Activating, and
Configuring Modules
The Apache software is built in a modular fashion: all functionality except some core
tasks is handled by modules. This has progressed so far that even HTTP is processed
by a module (http_core).
Apache modules can be compiled into the Apache binary at build time or dynamically
loaded at runtime. Refer to Section 40.4.2, "Activation and Deactivation" (page 764)
for details of how to load modules dynamically.
Apache modules can be divided into four different categories:
Base Modules
Base modules are compiled into Apache by default. Apache in SUSE Linux has
only mod_so (needed to load other modules) and http_core compiled in. All others
are available as shared objects: rather than being included in the server binary itself,
they can be included at runtime.
Extension Modules
In general, modules labeled as extensions are included in the Apache software
package, but are usually not compiled into the server statically. In SUSE Linux
Enterprise Server, they are available as shared objects that can be loaded into
Apache at runtime.
The Apache HTTP Server 763