Re: chroot'd apache -current

[Henning Brauer <lists-openbsd_(_at_)_bsws_(_dot_)_de>]

On Sun, Sep 01, 2002 at 03:12:03AM +1000, Warren J. Beckett wrote:
> Hi have a small problem with apache in the it's chroot env. 
> 
> All runs well until it is time for newsyslog to do it's work on my
> apache log files. What is happening is that after the logs have been
> rotated a SIGUSR1 is sent to apache which causes it to die with the
> following error in the error log.
> 
> [Sun Sep  1 02:54:35 2002] [notice] SIGHUP received.  Attempting to
> restart
> [Sun Sep  1 02:54:35 2002] [error] mod_ssl: Parent process could not
> create SSLMutex lockfile /var/www/logs/ssl_mutex.776 (System error
> follows)
> 
> Because at that point apache is in it's chroot it is trying to write now
> to /var/www/var/www/logs/ssl_mutex.776

your config file isn't current. we use a semaphore mutex now for that reason.

-- 
http://2suck.net/hhwl.html
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)