I'm following the description in Chap 8. of the Eagle Book for creating a module which adds configuration directives to Apache, however on my server version etc (see below), the first time through, the directive passes, but the directive gets rejected as an invalid command in the reload phase. Does the method in the Eagle book for defining directives no longer work, if this is the case, what can I do to have per-server variables such that I can use them at another modules initialisation time. MBM -------8<------- The server reports itself as Apache/1.3.11 (Unix) mod_perl/1.21 PHP/3.0.7 mod_ssl/2.5.0 OpenSSL/0.9.4 and [mbm@rigel]:~$ /usr/sbin/httpd -l Compiled-in modules: http_core.c mod_so.c mod_perl.c suexec: enabled; valid wrapper /usr/sbin/suexec [mbm@rigel]:~$ /usr/sbin/httpd -V Server version: Apache/1.3.11 (Unix) Server built: Feb 1 2000 21:17:00 Server's Module Magic Number: 19990320:6 Server compiled with.... -D EAPI -D EAPI_MM -D EAPI_MM_CORE_PATH="/var/run/httpd.mm" -D HAVE_MMAP -D HAVE_SHMGET -D USE_SHMGET_SCOREBOARD -D USE_MMAP_FILES -D USE_FCNTL_SERIALIZED_ACCEPT -D HTTPD_ROOT="/usr" -D SUEXEC_BIN="/usr/sbin/suexec" -D DEFAULT_PIDLOG="/var/run/httpd.pid" -D DEFAULT_SCOREBOARD="/var/run/httpd.scoreboard" -D DEFAULT_LOCKFILE="/var/run/httpd.lock" -D DEFAULT_XFERLOG="/var/log/httpd/access_log" -D DEFAULT_ERRORLOG="/var/log/httpd/error_log" -D TYPES_CONFIG_FILE="/etc/httpd/conf/mime.types" -D SERVER_CONFIG_FILE="/etc/httpd/conf/httpd.conf" -D ACCESS_CONFIG_FILE="/etc/httpd/conf/access.conf" -D RESOURCE_CONFIG_FILE="/etc/httpd/conf/srm.conf"
