From 083b7c672b4e65146db804202140e47e36c89d2b Mon Sep 17 00:00:00 2001
From: Rich Bowen mod_foo.so
you can use httpd.conf
file to load this module at server startup
or restart.
The DSO builds for individual modules can be disabled via
@@ -136,13 +136,13 @@ $ apxs -cia mod_foo.c
On modern Unix derivatives there exists a nifty mechanism
- usually called dynamic linking/loading of Dynamic Shared
+ On modern Unix derivatives there exists a mechanism
+ called dynamic linking/loading of Dynamic Shared
Objects (DSO) which provides a way to build a piece of
program code in a special format for loading it at run-time
into the address space of an executable program. This loading can usually be done in two ways: Automatically
+ This loading can usually be done in two ways: automatically
by a system program called The shared library approach is the typical one, because it
is what the DSO mechanism was designed for, hence it is used
for nearly all types of libraries the operating system
- provides. On the other hand using shared objects for extending
- a program is not used by a lot of programs.ld.so
when an
executable program is started or manually from within the
executing program via a programmatic system interface to the
@@ -221,8 +221,7 @@ $ apxs -cia mod_foo.c
httpd.conf
configuration commands instead of
- httpd.conf
configuration directives instead of
+ apxs -i
command followed by an apachectl restart
to
@@ -260,18 +258,14 @@ $ apxs -cia mod_foo.c
DSO has the following disadvantages: