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 !
I have now an other problem :
The apache is started, the process runs but the apache=20does 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......
Thanks
Di=E9go
Ivan Ristic (06/08/2004 11:01):
>die...@b-... wrote:
>> Hi,
>>
>> I have a problem with the Chroot directive.
>>
>> In my configuration file, i've writed the two directives that follow :
>>
>> Pidfile /opt/web/pids/pid-secure
>> .
>> .
>> SecChrootDir /opt/web
>>
>> And my apache does not start : in de errot log file, i can read :
>>
>> No such file or directory:could not create /opt/web/pids/pid-secure
>>
>> I'm sure that the rights are correct on the folders and when i delete the
>> SecChrootDir directive my apache works without problem.
>
> When you configure Apache like that it will attempt
> to create the pid file at /opt/web/opt/web/pids/pid-secure.
>
> The following should work provided there are no other problems:
>
> Pidfile /pids/pid-secure
>
>--
>ModSecurity (http://www.modsecurity.org)
>[ Open source IDS for Web applications ]
|
