Date: Tue, 5 Sep 2000 22:53:43 +0200 From: Peter van Dijk <peter@dataloss.net> To: current@freebsd.org Subject: Re: FIFOs & select: what about our implementation? Message-ID: <20000905225343.D2435@dataloss.net> In-Reply-To: <20000906004433.A72273@nagual.pp.ru>; from ache@nagual.pp.ru on Wed, Sep 06, 2000 at 12:44:33AM %2B0400 References: <20000905192458.A1428@dataloss.net> <Pine.BSF.4.21.0009060543430.25048-100000@besplex.bde.org> <20000906004433.A72273@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 06, 2000 at 12:44:33AM +0400, Andrey A. Chernov wrote: [snip] > > 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 > are two different things and behaviour of one thing not related to other. > Currently select indicates that data is available when it really isn't. I > don't ask to fix current read implementation, but select is just unusable > for FIFOs in its current form. I wouldn't say 'unusable'. It needs a work around. It is broken, in that selecting for readability on a pipe requires you to open that writing fd on it *everytime*. Greetz, Peter -- dataloss networks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000905225343.D2435>