[mod-security-users] Re: Mutex errors in chroot Apache

[Skye P. <sk...@f4...>]

Ivan Ristic <ivanr <at> webkreator.com> writes:
> 
>   You've probably left the mod_rewrite log outside the jail and
>   mod_rewrite does not like that. Move it back in.
> 

OK, I tried that.  No difference at all.  I didn't have RewriteLog on before.

The RewriteLog directive is not chrooted (to /home for me), it needed the full
path (/home/var/log/rewrite.log)

I even tried creating both a /home/var/log/ and a /home/home/var/log just in
case it was using the former before chroot and the latter after chroot, no luck.

Shouldn't all log files be opened before Apache is chrooted by mod_security? 
Seems like that is the case.

Here's a post I found with someone having the same problem:

http://www.telana.com/pipermail/peruser/2005-July/000078.html

quote: "it seems RewriteLogLevel 0 isnt enough

i commented out the following in mod_rewrite.c, and mod_rewrite still 
seems to work

     /*
     rv = apr_global_mutex_child_init(&rewrite_log_lock, NULL, p);
     if (rv != APR_SUCCESS) {
         ap_log_error(APLOG_MARK, APLOG_CRIT, rv, s,
                      "mod_rewrite: could not init rewrite log lock in 
child");
     }
     */
"

What is apr_global_mutex_child_init() doing?
I guess I'll look through the Apache2 source next.

Thanks,
Skye