Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 29592 invoked from network); 30 Mar 2009 18:34:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Mar 2009 18:34:25 -0000 Received: (qmail 78926 invoked by uid 500); 30 Mar 2009 18:34:25 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 78821 invoked by uid 500); 30 Mar 2009 18:34:24 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 78812 invoked by uid 99); 30 Mar 2009 18:34:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2009 18:34:24 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of trawick@gmail.com designates 72.14.220.157 as permitted sender) Received: from [72.14.220.157] (HELO fg-out-1718.google.com) (72.14.220.157) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2009 18:34:17 +0000 Received: by fg-out-1718.google.com with SMTP id e21so735411fga.22 for ; Mon, 30 Mar 2009 11:33:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=U500TRsnhcp8LfXzxbI0oH9J1v+o5ou4i+xoiiMnOfw=; b=hxwG/c+D4zquGKK8Y92cV6ZyAwAHXh03x42O0g/YJ5hb579nre1PBy9feUoaDZDGY7 uPImM2+vYFP4E9+2WqQgq8B67vBMfcW1mMqIxdKCi9qdhWrBB3nf49bdFUA2G/WZD4NZ Z5LLLva8FSJIU8H8mWimHhFcppaJ8tHFIt0m0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=vgvTEx6sX123tYefagepR3dsbVx6UYtcdsfE0sQALX5Wp5fLfzk178bJTQbPmJGOCK VWf1tiOgJkjAXFErGZQZ0xYVYLwVhww02RJFxzlXAZk7j/BezdRphsQ4ML5tUhBEHoBE yTGiqE7bct6MSLNMV/+4bJQwoSc2V6ncKX3z4= MIME-Version: 1.0 Received: by 10.86.61.13 with SMTP id j13mr2435686fga.68.1238438036668; Mon, 30 Mar 2009 11:33:56 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Mar 2009 14:33:56 -0400 Message-ID: Subject: Re: Posix sems still not recommended? From: Jeff Trawick To: "dev@apr.apache.org List" Content-Type: multipart/alternative; boundary=000e0cd24e2240888204665a53ff X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd24e2240888204665a53ff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Mon, Mar 30, 2009 at 2:07 PM, Jim Jagielski wrote: > Anyone know if: > > # POSIX semaphores and cross-process pthread mutexes are not > # used by default since they have less desirable behaviour when > # e.g. a process holding the mutex segfaults. > > is still applicable, at least for posix sems? AFAIK, the Solaris-specific recovery logic for cross-process pthread mutexes has been working reliably for a long time, but with the current wind direction APR is choosing fcntl(), which has sysdef implementations on that platform. no clues here about the POSIX semaphores -- Born in Roswell... married an alien... --000e0cd24e2240888204665a53ff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Mar 30, 2009 at 2:07 PM, Jim Jag= ielski <jim@jagunet= .com> wrote:
Anyone know if:

=A0# POSIX semaphores and cross-process pthread mutexes are not
=A0# used by default since they have less desirable behaviour when
=A0# e.g. a process holding the mutex segfaults.

is still applicable, at least for posix sems?

AFAIK, t= he Solaris-specific recovery logic for cross-process pthread mutexes has be= en working reliably for a long time, but with the current wind direction AP= R is choosing fcntl(), which has sysdef implementations on that platform.

no clues here about the POSIX semaphores

--
Born= in Roswell... married an alien...
--000e0cd24e2240888204665a53ff--