Getting Cgi Scripts To Work - Novell LINUX ENTERPRISE SERVER 11 - ADMINISTRATION Administration Manual

contains the apxs2 tools, which are necessary for compiling additional modules for
Apache.
apxs2 enables the compilation and installation of modules from source code (including
the required changes to the configuration files), which creates dynamic shared objects
(DSOs) that can be loaded into Apache at runtime.
The apxs2 binaries are located under /usr/sbin:
• /usr/sbin/apxs2—suitable for building an extension module that works with
any MPM. The installation location is /usr/lib/apache2.
• /usr/sbin/apxs2-prefork—suitable for prefork MPM modules. The instal-
lation location is /usr/lib/apache2-prefork.
• /usr/sbin/apxs2-worker—suitable for worker MPM modules. The instal-
lation location is /usr/lib/apache2-worker.
Install and activate a module from source code with the commands cd
/path/to/module/source; apxs2 -cia mod_foo.c (-c compiles the
module, -i installs it, and -a activates it). Other options of apxs2 are described in
the apxs2(1) man page.

27.5 Getting CGI Scripts to Work

Apache's Common Gateway Interface (CGI) lets you create dynamic content with
programs or scripts usually referred to as CGI scripts. CGI scripts can be written in any
programming language. Usually, script languages such as Perl or PHP are used.
To enable Apache to deliver content created by CGI scripts, mod_cgi needs to be acti-
vated. mod_alias is also needed. Both modules are enabled by default. Refer to
tion 27.4.2, "Activation and Deactivation"
WARNING: CGI Security
Allowing the server to execute CGI scripts is a potential security hole. Refer to
Section 27.7, "Avoiding Security Problems"
398 Administration Guide
(page 392) for details on activating modules.
(page 407) for additional information.
Sec-