From: Joshua Slive
Date: Tue, 10 Jul 2001 19:22:40 +0000 (+0000)
Subject: New directives should really come with documentation. This is
X-Git-Tag: 2.0.21~70
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ae4298616f498aeaefb5155cc3069dde1ef6c21f;p=apache
New directives should really come with documentation. This is
my best guess at what the documentation for the AcceptMutex directive
should look like.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@89533 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/directives.html b/docs/manual/mod/directives.html
index 6eceb5b211..e9bd65918f 100644
--- a/docs/manual/mod/directives.html
+++ b/docs/manual/mod/directives.html
@@ -24,6 +24,7 @@ listed here. They are described using a consistent format, and there is
of the terms used in their descriptions available.
+- AcceptMutex
- AccessFileName
- Action
- AddAlt
diff --git a/docs/manual/mod/prefork.html b/docs/manual/mod/prefork.html
index 26372a9ed5..3afba13b74 100644
--- a/docs/manual/mod/prefork.html
+++ b/docs/manual/mod/prefork.html
@@ -80,6 +80,7 @@ Apache uses.
Directives
+- AcceptMutex
- CoreDumpDirectory
- Group
- PidFile
@@ -99,6 +100,62 @@ Apache uses.
+
+Syntax: AcceptMutex default|method
+Default: AcceptMutex default
+Context: server config
+Status: core
+
+The AcceptMutex
directives sets the method that Apache
+uses to serialize multiple children accepting requests on network
+sockets. Prior to Apache 2.0, the method was selectable only at
+compile time. The optimal method to use is highly architecture and
+platform dependent. For further details, see the performance tuning
+documentation.
+
+If this directive is set to default
, then the
+compile-time selected default will be used. Other possible
+methods are listed below. Note that not all methods are available
+on all platforms. If a method is specified which is not available,
+a message will be written to the error log listing the available
+methods.
+
+
+
+flock
+- uses the
flock(2)
system call to lock the
+file defined by the LockFile
+directive.
+
+fcntl
+- uses the
fnctl(2)
system call to lock the
+file defined by the LockFile
+directive.
+
+sysvsem
+- uses SySV-style semaphores to implement the mutex.
+
+proc_pthread
+- uses POSIX mutexes as implemented by the POSIX Threads (PThreads)
+specification.
+
+
+
+
+