httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-2.0/docs/manual/mod prefork.html directives.html
Date Tue, 10 Jul 2001 19:22:44 GMT
slive       01/07/10 12:22:43

  Modified:    docs/manual/mod prefork.html directives.html
  New directives should really come with documentation.  This is
  my best guess at what the documentation for the AcceptMutex directive
  should look like.
  Revision  Changes    Path
  1.5       +57 -0     httpd-2.0/docs/manual/mod/prefork.html
  Index: prefork.html
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/prefork.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -d -b -u -r1.4 -r1.5
  --- prefork.html	2001/02/16 19:00:02	1.4
  +++ prefork.html	2001/07/10 19:22:39	1.5
  @@ -80,6 +80,7 @@
  +<li><a href="#acceptmutex">AcceptMutex</a>
   <li><a href="mpm_common.html#coredumpdirectory">CoreDumpDirectory</a></li>
   <li><a href="mpm_common.html#group">Group</a></li>
   <li><a href="mpm_common.html#pidfile">PidFile</a></li>
  @@ -98,6 +99,62 @@
  +<H2><A NAME="AcceptMutex">AcceptMutex Directive</A></H2>
  + HREF="directive-dict.html#Syntax"
  + REL="Help"
  +><STRONG>Syntax:</STRONG></A> AcceptMutex default|<EM>method</EM><BR>
  + HREF="directive-dict.html#Default"
  + REL="Help"
  +><STRONG>Default:</STRONG></A> <code>AcceptMutex default</code><BR>
  + HREF="directive-dict.html#Context"
  + REL="Help"
  +><STRONG>Context:</STRONG></A> server config<BR>
  + HREF="directive-dict.html#Status"
  + REL="Help"
  +><STRONG>Status:</STRONG></A> core</p>
  +<p>The <code>AcceptMutex</code> 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 <a
  +href="../misc/perf-tuning.html">performance tuning</a>
  +<p>If this directive is set to <code>default</code>, 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
  +<dd>uses the <code>flock(2)</code> system call to lock the
  +file defined by the <a href="mpm_common.html#lockfile">LockFile</a>
  +<dd>uses the <code>fnctl(2)</code> system call to lock the
  +file defined by the <a href="mpm_common.html#lockfile">LockFile</a>
  +<dd>uses SySV-style semaphores to implement the mutex.</dd>
  +<dd>uses POSIX mutexes as implemented by the POSIX Threads (PThreads)
   <H2><A NAME="maxspareservers">MaxSpareServers directive</A></H2>
   <!--%plaintext &lt;?INDEX {\tt MaxSpareServers} directive&gt; -->
  1.80      +1 -0      httpd-2.0/docs/manual/mod/directives.html
  Index: directives.html
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/directives.html,v
  retrieving revision 1.79
  retrieving revision 1.80
  diff -u -d -b -u -r1.79 -r1.80
  --- directives.html	2001/05/30 08:37:27	1.79
  +++ directives.html	2001/07/10 19:22:40	1.80
  @@ -24,6 +24,7 @@
   of the terms used in their descriptions available.
  +<LI><A HREF="prefork.html#acceptmutex">AcceptMutex</A>
   <LI><A HREF="core.html#accessfilename">AccessFileName</A>
   <LI><A HREF="mod_actions.html#action">Action</A>
   <LI><A HREF="mod_autoindex.html#addalt">AddAlt</A>

View raw message