[mod-security-users] Re: DocumentRoot path

[Julius S. <us...@zg...>]

Ivan Ristic wrote:
>> I understand. Is there any way to check then if it really is chrooted?
> 
> 
>   There will be two messages in the error log. Also, I think
>   mod_security exists if chroot fails.
> 
>   To be sure, why don't you create an empty /var/www? That way,
>   you will only see the content if the chroot is successful.
Good idea :)

> 
>> This also seems to be a work-around. Is this known problem with 
>> mod_security?
> 
> 
>   No, not really. It's a drawback of the approach, and the fact
>   was not built to support an internal chroot. Therefore it
>   performs some actions before the chroot and some after. There's
>   nothing we can do about that.
> 
I understand.

Now when I run the server with the module, I get the following errors in 
my logs though when I try to access the server:
[Thu Apr 14 16:02:01 2005] [notice] child pid 3787 exit signal 
Segmentation fault (11)
[Thu Apr 14 16:02:02 2005] [notice] child pid 3788 exit signal 
Segmentation fault (11)
[Thu Apr 14 16:03:05 2005] [notice] child pid 3789 exit signal 
Segmentation fault (11)
[Thu Apr 14 16:03:36 2005] [notice] child pid 3790 exit signal 
Segmentation fault (11)

The client recieves an empty page. When I do not use the module, 
everything seems to work correctly though.

Did I forgot anything?

Thanks,
Julius