You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by re...@apache.org on 2003/06/25 19:25:34 UTC
cvs commit: httpd-2.0/docs/manual/mod mpm_common.xml
rederpj 2003/06/25 10:25:34
Modified: docs/manual/mod mpm_common.xml
Log:
Added a warning to the AcceptMutex directive documentation indicating
that the pthread option can result in a non-responsive server on
systems that can't reclaim a locked mutex from the segfaulted child
holding it. [Paul J. Reder]
Revision Changes Path
1.30 +16 -0 httpd-2.0/docs/manual/mod/mpm_common.xml
Index: mpm_common.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mpm_common.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- mpm_common.xml 17 May 2003 19:32:02 -0000 1.29
+++ mpm_common.xml 25 Jun 2003 17:25:34 -0000 1.30
@@ -62,6 +62,22 @@
>LogLevel</directive> to <code>debug</code>. Then the default <directive
>AcceptMutex</directive> will be written into the <directive
module="core">ErrorLog</directive>.</p>
+
+ <note type="warning"><strong>Warning:</strong>
+ <p>On most systems, when the <code>pthread</code> option
+ is selected, if a child process terminates abnormally
+ while holding the <code>AcceptCntl</code> mutex the
+ server will stop responding to requests. When this
+ occurs, the server will require a manual restart to
+ recover.</p>
+ <p>Solaris is a notable exception as it provides a
+ mechanism, used by Apache, which usually allows the
+ mutex to be recovered after a child process terminates
+ abnormally while holding a mutex.</p>
+ <p>If your system implements the
+ <code>pthread_mutexattr_setrobust_np()</code> function,
+ you may be able to use the <code>pthread</code> option safely.</p>
+ </note>
</usage>
</directivesynopsis>