Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 37328 invoked by uid 500); 30 Jun 2001 20:43:00 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 37315 invoked from network); 30 Jun 2001 20:42:59 -0000 Message-ID: <009901c101a4$670fd640$6501a8c0@apache> From: "Bill Stoddard" To: References: Subject: Re: [PATCH] Allow pthread_mutex_t to be a cross-process lock Date: Sat, 30 Jun 2001 16:36:47 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > 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