Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <3F5C68E0.9070207@attglobal.net>
Date: Mon, 08 Sep 2003 07:32:48 -0400
From: Jeff Trawick <trawick@attglobal.net>
Reply-To: trawick@attglobal.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Anthony Howe <achowe@snert.com>
CC: dev@apr.apache.org
Subject: Re: apr_global_mutex_child_init & mod_watch
References: <3F5B53C8.3010500@snert.com> <3F5B58B3.7040901@attglobal.net>
 <3F5B5E03.4010604@snert.com> <3F5B7406.2040808@attglobal.net>
 <3F5B7AC1.2070209@snert.com> <3F5BB643.3030205@attglobal.net>
 <3F5C4DF5.8050507@snert.com>
In-Reply-To: <3F5C4DF5.8050507@snert.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Anthony Howe wrote:

>> flock is used on FreeBSD by default...  flock requires that chmod be 
>> done on the lock in the child init
> 
> 
> As an aside, why is flock() used on FreeBSD?

historical reasons?

>> at Apache 2.0.48-dev, you have to do the chmod() on the lock file, 
>> like mod_ssl does in that branch
> 
> 
> OK. Is there an API that returns what the APR_LOCK_DEFAULT mutex will be?

not exactly, but there is an API that will give you the info you need: 
apr_proc_mutex_name(); pass it a mutex and it returns a string such as 
"sysvsem", "flock", "fcntl", etc. to indicate what mechanism is in use

alternatively, if APR_USE_FLOCK_SERIALIZE is defined in apr.h then the 
default is flock
> That would be the ideal solution, but I'm not sure I can wait until 
> 2.0.48. Plus not everyone upgrades when they should, so I need a work 
> around.

probably won't be in 2.0.48 anyway

> BTW are there any version macros in Apache 2 or the APR like:
> 
>     APACHE_VERSION_MAJOR
>     APACHE_VERSION_MINOR

see ap_release.h for similar

>     APR_VERSION_MAJOR
>     APR_VERSION_MINOR

see apr_version.h for similar