On Tue, 2004-11-02 at 15:35, Stas Bekman wrote:
> Cory Omand wrote:
> 
> [First of all, don't forget to reply-all, when following up on list's 
> threads. Thanks.]

Sorry -- force of habit.

> >>It has nothing to do with either A-T or mod_perl, A-T just per-uses the 
> >>globally installed httpd.conf for its configuration. So the problem is 
> >>there. Change that file (you can see exactly which one by running t/TEST 
> >>-conf -trace=debug) to do the right thing and everything will work just fine.
> > 
> > 
> > The globally installed configuration on my build system does not change
> > the default AcceptMutex.  If I add 'AcceptMutex pthread', in
> > Apache::TestConfig, then t/conf/httpd.conf will contain this line. 
> > Running TEST -conf as you suggested above does indicate that the global
> > configuration is 'inherited' for the test, and loads all of the
> > appropriate modules...
> > 
> > At any rate, should TestConfig not generate a config which relies only
> > on paths that are writable by the current user?  Shouldn't directives
> > that rely on filesystem access (scoreboards, mutexes, etc) create/access
> > files only under 't' when running configs created by A-T (e.g. setting
> > 'LockFile' for threaded MPMs)?
> 
> But Apache-Test does not add any of those directives!

I'm not sure we're talking about the same thing here...  I am talking
about the httpd.conf that gets generated during 'make test' for mp2
1.99_17.  The module Apache::TestConfig included with mp2 appears to be
generating parts of the file 't/conf/httpd.conf', specifically the block
that starts '<IfModule worker.c>', as my httpd binary is built using the
worker MPM.

> Ideally A-T should have no such special case knowledge since it makes 
> things a way too complicated to maintain and introduces lots of problems.

I understand that A-T itself should not have any knowledge of the system
it's testing -- but the specific implementation of tests for mp2
should...  If it's possible to run the tests for mp2 as a non-root user,
it really makes no sense to assume the non-root user can start up the
default apache configuration, does it?

> It goes along these lines: You should be able to start Apache w/o 
> mod_perl, i.e. your global httpd.conf should be correct. When this works, 
> Apache-Test will use that config file to get the configuration for the 
> modperl (and any other) tests, adding extra things on top.

It is correct, as root is able to start apache 2 without mod_perl.  I
cannot start apache with the global configuration because the default
paths for apache logs, acceptmutex, etc. are not writable by anyone but
root.

> So the solution here is to fix your global httpd.conf and the rest will 
> work. Does that do the trick for you?

Does the above clarify where I'm coming from?

Regards,
Cory.


-- 
Cory Omand <[EMAIL PROTECTED]>


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Reply via email to