httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Bloom" <...@covalent.net>
Subject RE: Config path brokenness
Date Thu, 07 Mar 2002 14:22:01 GMT
> * Brian Havard (brianh@kheldar.apana.org.au) wrote :
> > With the current HEAD (configured using --prefix=/Apps/apache2), I
get
> the
> > following in my ap_config_auto.h:
> >
> > /* Location of the config file, relative to the Apache root
directory */
> > #define SERVER_CONFIG_FILE "/Apps/apache2/conf/httpd.conf"
> >
> > whereas in, say, 2.0.32 it reads:
> >
> > /* Location of the config file, relative to the Apache root
directory */
> > #define SERVER_CONFIG_FILE "conf/httpd.conf"
> >
> >
> > What this means is that I can no longer run the server with an
alternate
> > server root using the -d switch, something I commonly do to test
running
> in
> > the build tree without having to make install. It's also commonly
used
> by
> > users of binary builds if they want to install to a directory other
than
> > what the binary builder specified.
> >
> > I know this stuff's been hacked at recently, I just want to let
people
> know
> > it's not finished yet :)
> >
> use -d /path -f /path/to/conf/file

That's not good enough Thom.  The -d must be able to work on its own.
That's why we allow relative paths for just about everything.

Ryan



Mime
View raw message