From owner-freebsd-hackers Sun Nov 23 20:11:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA00983 for hackers-outgoing; Sun, 23 Nov 1997 20:11:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA00976 for ; Sun, 23 Nov 1997 20:11:37 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA22956; Sun, 23 Nov 1997 20:02:35 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd022954; Sun Nov 23 20:02:27 1997 Date: Sun, 23 Nov 1997 20:00:19 -0800 (PST) From: Julian Elischer To: Alex Nash cc: deischen@iworks.InterWorks.org, freebsd-hackers@freebsd.org Subject: Re: pthread_cond_timedwait returning wrong error? In-Reply-To: <199711232301.RAA19042@zen.nash.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk don't forget 2.2.x (it has basically the same code) On Sun, 23 Nov 1997, Alex Nash wrote: > 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 > > >