From apache-cvs-return-6612-apmail-apache-cvs-archive=apache.org@apache.org Tue Jul 10 19:23:52 2001 Return-Path: Delivered-To: apmail-apache-cvs-archive@apache.org Received: (qmail 91914 invoked by uid 500); 10 Jul 2001 19:23:11 -0000 Mailing-List: contact apache-cvs-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-cvs@apache.org Received: (qmail 91626 invoked by uid 500); 10 Jul 2001 19:22:55 -0000 Delivered-To: apmail-httpd-2.0-cvs@apache.org Date: 10 Jul 2001 19:22:44 -0000 Message-ID: <20010710192244.91459.qmail@apache.org> From: slive@apache.org To: httpd-2.0-cvs@apache.org Subject: cvs commit: httpd-2.0/docs/manual/mod prefork.html directives.html slive 01/07/10 12:22:43 Modified: docs/manual/mod prefork.html directives.html Log: 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 @@

Directives

    +
  • AcceptMutex
  • CoreDumpDirectory
  • Group
  • PidFile
  • @@ -98,6 +99,62 @@


    + +

    AcceptMutex Directive

    +

    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.
    + +
    + +

    MaxSpareServers directive

    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.