Cory Omand wrote: [...]
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
No, my global httpd.conf doesn't have an active LockFile directive (there is one in there, but it's commented out by default). I think the issue is that my server is compiled to store logs in var/log/*_log, rather than 'logs/*'. The path to logs during the test is overridden to be 'logs/', relative to the 't' directory, but LockFile (and maybe other directives that would write into the log directory) attempts to create the lock as 'var/log/accept.lock'. Obviously this cannot succeed, as there is no 'var' directory in there.
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
I've added this into TestConfig.pm, and am testing right now...
<IfModule !mpm_winnt.c> <IfModule !mpm_netware.c>
Lockfile @t_logs@/accept.lock
</IfModule>
</IfModule>
OK, let us know if that has worked. I hope we can add that for any mpm, and not just netware, since LockFile seems to be a global core option. Am I right?
-- __________________________________________________________________ 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
