Re: [mod-security-users] Chroot problem

[Ivan R. <iv...@we...>]

die...@b-... wrote:

> Thank u very much.
> 
> The error message has disappeard.
> 
> It's quite strange that you can not write the entire path in de configuation
> file to access to the pid !

  It's not strange, that's how chroot works. You can no longer use the
  entire path after the chroot(2) call has been made.


> I have now an other problem :
> 
> The apache is started, the process runs but the apache does not respond to any
> request : there are no child processes......
> 
> In the access log file, there is no trace of request and in the error log file,
> there is no error but there is a new message with the level (emergency) : No
> such file or directory : Couldn't create accept lock !!!!
> 
> If someone has an idea......

  Send the httpd.conf and the filesystem layout to the list
  and we might be able to help.

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]