From owner-freebsd-hackers Sun Nov 23 15:05:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA08920 for hackers-outgoing; Sun, 23 Nov 1997 15:05:12 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA08896 for ; Sun, 23 Nov 1997 15:05:04 -0800 (PST) (envelope-from alex@zen.nash.org) Received: (from alex@localhost) by zen.nash.org (8.8.8/8.8.7) id RAA19042; Sun, 23 Nov 1997 17:01:37 -0600 (CST) (envelope-from alex) Message-Id: <199711232301.RAA19042@zen.nash.org> Date: Sun, 23 Nov 1997 17:01:37 -0600 (CST) From: Alex Nash Reply-To: nash@mcs.com Subject: Re: pthread_cond_timedwait returning wrong error? To: deischen@iworks.InterWorks.org cc: freebsd-hackers@freebsd.org In-Reply-To: <199711232120.PAA23932@iworks.InterWorks.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 23 Nov, Daniel M. Eischen wrote: > > Is EAGAIN the correct error for a timeout from a > pthread_cond_timedwait() call? I would think that > ETIMEDOUT would be more appropriate. According to my 1996 edition of ANSI/IEEE std 1003.1, you are correct -- ETIMEDOUT should be returned. I've committed a fix for this into -current. Thanks. Alex