Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 58426 invoked by uid 500); 22 May 2002 17:46:37 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 58399 invoked from network); 22 May 2002 17:46:36 -0000 Reply-To: From: "Ryan Bloom" To: Subject: RE: [PATCH 2] worker MPM deadlock Date: Wed, 22 May 2002 10:44:30 -0700 Organization: Covalent Technologies Message-ID: <001001c201b8$534c3a30$8800000a@KOJ> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20020522103453.B26886@clove.org> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Aaron Bannert [mailto:aaron@clove.org] > > On Wed, May 22, 2002 at 01:31:06PM -0400, Bill Stoddard wrote: > > Yep this is a problem. I believe the pthread spec states that the > cond_wait can be > > spuriously triggered. > > I'm pretty sure it does, which is why we always check for the condition > when we wake up and go right back to sleep if the condition hasn't been > met. I'll raise you and say without a doubt, pthread_cond can be triggered spuriously. Ryan