From: Paul J. Reder
Date: Wed, 25 Jun 2003 17:25:34 +0000 (+0000)
Subject: Added a warning to the AcceptMutex directive documentation indicating
X-Git-Tag: pre_ajp_proxy~1511
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=745afde49ab26bc99a78a799468447b32152bdbc;p=thirdparty%2Fapache%2Fhttpd.git
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]
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@100358 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/mpm_common.xml b/docs/manual/mod/mpm_common.xml
index c007c1f3894..ac6ba7da419 100644
--- a/docs/manual/mod/mpm_common.xml
+++ b/docs/manual/mod/mpm_common.xml
@@ -62,6 +62,22 @@ accepting requests on network sockets
>LogLevel to debug. Then the default AcceptMutex will be written into the ErrorLog.
+
+ Warning:
+ On most systems, when the pthread option
+ is selected, if a child process terminates abnormally
+ while holding the AcceptCntl mutex the
+ server will stop responding to requests. When this
+ occurs, the server will require a manual restart to
+ recover.
+ 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.
+ If your system implements the
+ pthread_mutexattr_setrobust_np() function,
+ you may be able to use the pthread option safely.
+