Cory Omand wrote:
On Tue, 2004-11-02 at 16:19, Stas Bekman wrote:

Does your global httpd.conf has an AcceptMutex entry which specifies a location which is only root accessible? So A-T should probably detect that and rewrite the path to something local (e.g. t/logs/acceptmutex)?


The global httpd.conf file, which is the default file distributed with
apache 2.0.52, does not have an AcceptMutex or LockFile entry.  By
default 'LockFile' points to 'logs/accept.lock' (per the apache 2.0
docs).  My fix to get the mp2 tests to start was to patch the
@THREAD_MODULE@ section of 'Apache-Test/lib/Apache/TestConfig.pm' to set
'AcceptMutex pthread'.  That's not going to be a good solution, as there
is no guarantee that everyone else has pthread mutexes.

that's correct.

 I'm also not
familiar enough with A-T to know if there's a global variable that
points to the local logging directory (e.g. where mp2 writes the
error_log).

it's @t_logs@

 Assuming that this variable is available as @APACHE_LOGS@,
it would be possible to set 'LockFile @APACHE_LOGS@/accept.lock' in the
@THREAD_MODULE@ section...

Oh, you mean we were talking about LockFile all this time, which is wrong when run under non-root user, right? So your global httpd.conf has:


LockFile logs/accept.lock

which is picked by Apache-Test and put into t/conf/httpd.conf? In which case we should rewrite this setting to point to:

LockFile @t_logs@/accept.lock

but since the server starts from t/, logs/accept.lock should already point there. Or does your global httpd.conf has a hardcoded full path to LockFile?


-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com

--
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