Owen Boyle wrote:
>
> Maarten van Lieshout wrote:
> >
> > This problem has been reported previously, but I am using different
> > software versions.
> > SSLMutex file:chroot/tmp/ssl_mutex
>
> What all this "chroot" stuff? This is supposed to be a full path to a
> filename. Try something simple like:
>
> SSLMutex file:/home/apache/logs/ssl_mutex
chroot means it runs in its own root-enviroment, so there is no need to
enter the full pathname. I have tried it just to be sure, but it didn't
work.
>
> NB apache appends the child process id to this so each lock-file is
> unique - you don't need to worry about assiging different locks to
> different VHs or servers.
>
> > [04/Apr/2001 23:46:57 97322] [error] Child could not open SSLMutex
> > lockfile /home/www.nottherealname.com/chroot/tmp/ssl_mutex.89573 (System error
>follows)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
See what I mean? It cannot find the file ssl_mutex.89573 which DOES
exist. I think this is a bug in modssl.
> > [04/Apr/2001 23:46:57 97322] [error] System: No such file or directory
> > (errno: 2)
>
> It means what is says: tried to open a file called
> "/home/www.nottherealname.com/chroot/tmp/ssl_mutex.89573" but couldn't
> because the directory doesn't exist...
>
> Rgds,
>
> Owen Boyle.
Regards,
Maarten van Lieshout
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
