From owner-freebsd-bugs Tue Oct 16 10:10: 6 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 14CAA37B403 for ; Tue, 16 Oct 2001 10:10:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9GHA2K96407; Tue, 16 Oct 2001 10:10:02 -0700 (PDT) (envelope-from gnats) Date: Tue, 16 Oct 2001 10:10:02 -0700 (PDT) Message-Id: <200110161710.f9GHA2K96407@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Garrett Wollman Subject: Re: kern/19871 select on named pipes always returns 'available for reading' Reply-To: Garrett Wollman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/19871; it has been noted by GNATS. From: Garrett Wollman To: Bruce Evans Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/19871 select on named pipes always returns 'available for reading' Date: Tue, 16 Oct 2001 13:01:12 -0400 (EDT) < said: > work. It just says that select() returns if one of the read descriptors > is "ready to read". It doesn't seem to define "ready to read", of course I thought that we had agreed that select would consider ``ready'' as meaning ``a read (or write, as appropriate) system call on this file descriptor would return without blocking, provided you win any races''. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message