From owner-freebsd-current Wed Apr 22 15:36:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19705 for freebsd-current-outgoing; Wed, 22 Apr 1998 15:36:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlogic.com.au [203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19692 for ; Wed, 22 Apr 1998 22:36:02 GMT (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id IAA00643; Thu, 23 Apr 1998 08:34:51 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804222234.IAA00643@cimlogic.com.au> Subject: Re: pthread_mutex_lock In-Reply-To: <199804222228.RAA15757@compound.east.sun.com> from Tony Kimball at "Apr 22, 98 05:28:54 pm" To: alk@pobox.com Date: Thu, 23 Apr 1998 08:34:51 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Kimball wrote: > > I was of the impression that pthread_mutex_lock was supposed to block? > The man page on current says it does not. Am I confused? Is the > man page confused? Or is it a discrepancy between implementation > and spec, documented by the man page? It blocks. pthread_mutex_trylock is the one that doesn't block. Which man page says otherwise? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message