Brad,
Look at the first hooks of the win32 project. We 'do our own thing'. This
aught to be a portable behavior (e.g., build with HTTPD_RELATIVE_ROOT defined?)
Bill
----- Original Message -----
From: "Brad Nicholes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 12, 2001 5:36 PM
Subject: Hard coded HTTPD_ROOT in httpd.h...
In httpd.h there are a number of hard coded paths that define the default server
home directory. Looking at the code, it appears
that if the user does not specify a -f parameter when starting apache, it will
automatically look for the .CONF file in
HTTPD_ROOT/conf/httpd.conf. This means that if HTTPD_ROOT for platform XX is defined
as "/apache" but the user decided to install
apache to "/apch", Apache would never find the httpd.conf file unless the -f
<location> is defined on the command line. Leaving the
default hard coded on NetWare would cause a problem. If HTTPD_ROOT were defined as
"/apache" as on other platforms, NetWare will
always default to "SYS:/Apache" which it many cases would be wrong since most apache
users do not install add on software on the
SYS: volume. Hard coding a volume name would always be wrong since the volume name is
a user definable value. Wouldn't it make
more since to define the default server home directory as getcwd() instead of a hard
coded path?
thanks,
Brad
