Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2F70D119C8 for ; Wed, 3 Sep 2014 16:57:00 +0000 (UTC) Received: (qmail 77370 invoked by uid 500); 3 Sep 2014 16:56:50 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 77335 invoked by uid 500); 3 Sep 2014 16:56:50 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 77325 invoked by uid 99); 3 Sep 2014 16:56:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Sep 2014 16:56:50 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mike.rumph@oracle.com designates 141.146.126.69 as permitted sender) Received: from [141.146.126.69] (HELO aserp1040.oracle.com) (141.146.126.69) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Sep 2014 16:56:20 +0000 Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s83GuISQ013383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 3 Sep 2014 16:56:19 GMT Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s83GuH7V019974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 3 Sep 2014 16:56:18 GMT Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s83GuHPR019965 for ; Wed, 3 Sep 2014 16:56:17 GMT Received: from [10.132.185.146] (/10.132.185.146) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 03 Sep 2014 09:56:17 -0700 Message-ID: <54074830.5050102@oracle.com> Date: Wed, 03 Sep 2014 09:56:16 -0700 From: Mike Rumph Organization: Oracle Corporation User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: users@httpd.apache.org References: <5406A2BC.5050401@gmail.com> In-Reply-To: <5406A2BC.5050401@gmail.com> Content-Type: multipart/alternative; boundary="------------050101040309050002000203" X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Understanding Apache Mutex directive. --------------050101040309050002000203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello dE, I can only give you my own interpretation of this document. First of all the Mutex directive in Apache httpd 2.4.x replaces several different directives from Apache httpd 2.2.x. The SVN commit for this is 883540. - http://svn.apache.org/viewvc?view=revision&revision=883540 The phrase "the first argument" in both cases probably means the first argument after the mechanism. The doc should be worded more clearly. (So this should probably changed to "the second argument".) The mechanism is what kind of mutex technology is used. Apache httpd uses several different mutexes for different purposes. The mutex-name specifies which of these mutexes the Mutex directive applies to. It is a little confusing that either one of these arguments can have the value "default". So the phrase "The following mutex /mechanisms/ are available:" applies to the mechanism (argument 1). And the phrase "The following table documents" applies to the mutex-name (argument 2). I hope this helps. Thanks, Mike Rumph On 9/2/2014 10:10 PM, dE wrote: > Hi. > > I was reading this -- > > http://httpd.apache.org/docs/trunk/mod/core.html#mutex > > Quoting what's written here -- >> Specify |default| as the first argument to change the settings for >> all mutexes > As we know mutex is a mechanism; it appears Apache has settings for > each mutex it implements. > >> specify a mutex name (see table below) as the first argument to >> override defaults only for that mutex. > > So the table starting with 'The following table documents....' lists > all the mechanisms. But before the table there exists a list with the > heading 'The following mutex mechanisms are available:'. > > So I don't understand which one of these is the mutex mechanism. > > Also the statement -- > >> specify a mutex name (see table below) as the first argument to >> override defaults only for that mutex. > > Contradicts the examples -- > >> Mutex sysvsem default >> Mutex fcntl:/var/httpd/locks mpm-accept > > Where the entries in the table are not the first argument, instead the > list starting with 'The following mutex mechanisms are available:' is. > > Thanks for any clarification. --------------050101040309050002000203 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello dE,

I can only give you my own interpretation of this document.

First of all the Mutex directive in Apache httpd 2.4.x replaces several different directives from Apache httpd 2.2.x.
The SVN commit for this is 883540.
- http://svn.apache.org/viewvc?view=revision&revision=883540

The phrase "the first argument" in both cases probably means the first argument after the mechanism.
The doc should be worded more clearly.  (So this should probably changed to "the second argument".)

The mechanism is what kind of mutex technology is used.
Apache httpd uses several different mutexes for different purposes.
The mutex-name specifies which of these mutexes the Mutex directive applies to.
It is a little confusing that either one of these arguments can have the value "default".

So the phrase "The following mutex mechanisms are available:" applies to the mechanism  (argument 1).
And the phrase "The following table documents" applies to the mutex-name (argument 2).

I hope this helps.

Thanks,

Mike Rumph

On 9/2/2014 10:10 PM, dE wrote:
Hi.

I was reading this --

http://httpd.apache.org/docs/trunk/mod/core.html#mutex

Quoting what's written here --
Specify default as the first argument to change the settings for all mutexes
As we know mutex is a mechanism; it appears Apache has settings for each mutex it implements.

specify a mutex name (see table below) as the first argument to override defaults only for that mutex.

So the table starting with 'The following table documents....' lists all the mechanisms. But before the table there exists a list with the heading 'The following mutex mechanisms are available:'.

So I don't understand which one of these is the mutex mechanism.

Also the statement --

specify a mutex name (see table below) as the first argument to override defaults only for that mutex.

Contradicts the examples --

Mutex sysvsem default
Mutex fcntl:/var/httpd/locks mpm-accept

Where the entries in the table are not the first argument, instead the list starting with 'The following mutex mechanisms are available:' is.

Thanks for any clarification.

--------------050101040309050002000203--