LinuxSA Mailing list archives

  From: Alan Kennington <akenning@dog.topology.org>
  To  : Michael Kratz <michael_kratz@hotmail.com>
  Date: Sat, 24 Feb 2001 13:25:10 +1030

Re: Apache 1.3.14 httpd.conf problems

On Sat, Feb 24, 2001 at 12:17:25PM +1030, Michael Kratz wrote:
> 
> Thats what I did, and now its grizzling and does not seem to be reading the 
> httpd.conf file properly, however if i tell it to reload the conf file, ie 
>  >httpd reload, it does not come up with any errors.
> 
> Also now I have a few email from root saying that it cant find the logfiles 
> to rotate.


Michael,

That sounds very familiar.
This happens to me particularly when I reinstall from source.

The problem is the pesky --prefix parameter of ./configure in the
source directory.
People putting together distributions seem to change their
mind about exactly where to put log files and config files
every 6-12 months or so.

So now you just have to find out where the config and log files
_really_ are for your new installation.

The info could be embedded in some user manual - which often
gets modified to reflect the ./configure --prefix options.
Or you could go on a mad hunt.
Here are some places where I would look:

/usr/local/apache/conf/
/etc/httpd/
/etc/httpd/conf/
/home2/apache/conf/

These are obtained from "locate httpd.conf" on some of my machines.
Admittedly the /home2/apache/conf was one that I personally
entered as --prefix. But the others are quite common.

Every time I install new software now (like a new package from
source per day), I look to see what prefix it will use, and try
to set it to something sensible. If you're using an RPM,
you don't get much choice, I guess. 

Good luck with your hunting!

Cheers,
Alan Kennington.

-- 
LinuxSA WWW: http://www.linuxsa.org.au/  IRC: #linuxsa on irc.linux.org.au
To unsubscribe from the LinuxSA list:
  mail linuxsa-request@linuxsa.org.au with "unsubscribe" as the subject