Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <200309081219.h88CJM124130@devsys.jaguNET.com>
Subject: Re: apr_global_mutex_child_init & mod_watch
To: achowe@snert.com (Anthony Howe)
Date: Mon, 8 Sep 2003 08:19:19 -0400 (EDT)
Cc: trawick@attglobal.net, dev@apr.apache.org, dev@httpd.apache.org
Reply-To: jim@jaguNET.com
In-Reply-To: <no.id> from "Anthony Howe" at Sep 08, 2003 11:37:57 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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? It has SysV like mutexes 
> and POSIX ones too (at least in 4.8) - I may sound unsure cause I've 
> only recently switched platforms from Linux to FreeBSD just to be different.

Support for Posix sems was a "somewhat" new addition. SysV sems
were also not guarateed to be present (this is all old stuff by
the way, and inherited from 1.3)...

> 
> > 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?
> 

Check out apr_proc_mutex_name() and apr_proc_mutex_defname()

-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
      "A society that will trade a little liberty for a little order
             will lose both and deserve neither" - T.Jefferson