Geoffrey Young wrote:
Joe Orton wrote:
On Mon, Nov 19, 2007 at 11:45:59PM -0500, William McKee wrote:
On Mon, Nov 19, 2007 at 09:31:30AM +0000, Joe Orton wrote:
Debian/Ubuntu does not use httpd.conf to load modules; it uses
apache2.conf and loads the modules from a directory
(/etc/apache2/mods-enabled). mod_env, which provides the PassEnv
directive, is being loaded in this way. I guess A::T does not support
auto-detecting these modules yet. Is any work being done in this area?
I presume the "mods-enabled" directory contains config files included
via "Include" from the main configuration file? A::T follows "Include"
directives so this should work.
The apache.conf file contains the following two lines which load the
modules and any configuration directives:
Include /etc/apache2/mods-enabled/*.load
Include /etc/apache2/mods-enabled/*.conf
Should that work? Isn't there a way to debug or trace the config
process?
Yes, I think that should work. Can you try:
./t/TEST -conf -trace=debug
and follow the lines from "inheriting config file:" to see what happens.
fwiw, I just watched fred get caught by this exact thing at apachecon -
don't forget to nuke ~/.apache-test beforehand :)
Yeah that was no fun, and I don't think it was the first time it
happened to me. This suggestion may be too verbose for most people's
tastes, but it would be helpful to me to always have the 'inheriting
config file:' output present under normal A::T execution.
Most people have at least one httpd.conf file on their system, and those
with system installed apaches usually have /etc/httpd.conf also ( I did
and didn't know about it ).
