Re: Error using chroot functionality

Daniel Pinsky <danielpinsky@xxxxxxxxxxx> wrote:

> I compiled mod_security-1.8.2 into apache_1.3.31. Everything seems to be ok. 
> I wanted to chroot it to /chroot/apache. I also tried to bring the log files
> into the chrooted file system under /chroot/apache/logs/access_log ang
> error_log. When I try to start the service I get an error that [error] (2)No
> such file or directory: could not open transfer lof file
> /chroot/apache/logs/access_log
>
> The log and the directory do exist and the necessary file rights do exist!! 
> any help would be appreciated.

Could it be that you need to specify /logs/access_log as log directive? I'm
not familiar with mod_security's chroot feature but if you "manually" chroot
apache, you first call chroot() and afterwards apache evaluates the log
directive. That means that at the time apache reads its log directive there's
no more /chroot/apache/logs but only /logs. However, this could be wrong when
using mod_security to perform the chroot.


Regards,

Ulf

-- 
Ulf Stegemann
zeitform Internet Dienste



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com