From owner-freebsd-current Tue Sep 5 23:53:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 2FA6537B42C for ; Tue, 5 Sep 2000 23:53:21 -0700 (PDT) Received: (qmail 11832 invoked from network); 6 Sep 2000 06:53:16 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 6 Sep 2000 06:53:16 -0000 Date: Wed, 6 Sep 2000 17:53:08 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Andrey A. Chernov" Cc: Peter van Dijk , current@freebsd.org Subject: Re: FIFOs & select: what about our implementation? In-Reply-To: <20000906004433.A72273@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Sep 2000, Andrey A. Chernov wrote: > Please consider that we talk not about reads but about select. 'Select' is > used to indicate that data is available while 'read' used to read it, they No, select on a read descriptor returns successfully when the descriptor is "ready" to read, whatever that means. It normally means that a read on the descriptor would not block (even if O_NONBLOCK is not set). Reads of EOF satisfy this condition. This is normally the correct behaviour. E.g., it prevents programs reading stdin via select() loop from hanging when stdin is a pipe with no writers. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message