Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <009f01c101a5$1037f9a0$6501a8c0@apache>
From: "Bill Stoddard" <bill@wstoddard.com>
To: <dev@apr.apache.org>
References: <Pine.LNX.4.30.0106301315360.2151-100000@koj.rkbloom.net>
 <009901c101a4$670fd640$6501a8c0@apache>
Subject: Re: [PATCH] Allow pthread_mutex_t to be a cross-process lock
Date: Sat, 30 Jun 2001 16:41:27 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Ooops, send this to the wrong list...

Also my bad, Apache 1.3 does NOT default to pthread serialized accept on AIX, but that's what we
ship with IBM HTTP Server and it works much better than FCNTL on 8 way machines and above.

Bill

----- Original Message -----
From: "Bill Stoddard" <bill@wstoddard.com>
To: <new-httpd@apache.org>
Sent: Saturday, June 30, 2001 4:36 PM
Subject: Re: [PATCH] Allow pthread_mutex_t to be a cross-process lock


>
> > On Sat, 30 Jun 2001, Justin Erenkrantz wrote:
> >
> > > Can someone enlighten me as to why we have --with-pthread-cross and we
> > > aren't telling anyone?  If we have pthread.h, PTHREAD_PROCESS_SHARED,
> > > and pthread_mutexattr_setpshared, it seems reasonable enough to
> > > define USE_PROC_PTHREAD_SERIALIZE to 1.  Or, are pthread_mutex_t not
> > > suitable for cross-process locks for some other reason that we have to
> > > have a manual override?
> > >
> > > Unless someone says otherwise, I'll commit this tonight/tomorrow.
> >
> > In general, most platforms don't really support cross process pthread
> > mutex's.  Even those that have PTHREAD_PROCESS_SHARED tend to not work
> > properly.  For example, AIX has that defined, but they don't really
> > support pthread mutex's cross processes.
>
> PTHREAD_PROCESS_SHARED works for me on AIX 4.3.2 and later. And you will see this is the default
for
> Apache 1.3 for AIX.
>
> Are you seeing actual failures or going from memory of conversations past?
>
> Bill
>