DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8124>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8124
mod_ssl fails to get and release semaphore mutex
------- Additional Comments From martin.t.kutschker@blackbox.net 2002-04-16 14:28 -------
Andreas, mod_ssl does never user file based locking due to bug #8122, so no file
will show up. The warnings imply that mod_ssl is not using lock, so it's like
saying "SSLMutex none".
My theory is that Apache creates the semaphores and THEN switches user/group
locking mod_ssl out of shm/sem.
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8124>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8124
mod_ssl fails to get and release semaphore mutex
------- Additional Comments From martin.t.kutschker@blackbox.net 2002-04-16 14:28 -------
Andreas, mod_ssl does never user file based locking due to bug #8122, so no file
will show up. The warnings imply that mod_ssl is not using lock, so it's like
saying "SSLMutex none".
My theory is that Apache creates the semaphores and THEN switches user/group
locking mod_ssl out of shm/sem.