On Wed, Sep 06, 2000 at 07:35:50AM +1100, Bruce Evans wrote:
> This behaviour is sort of intentional.  Reads on a named pipe with no
> writers are specified by POSIX.1 to return immediately.  4.4BSD does
> extra work to break this in some cases.  select() on a read descriptor
> open on such a pipe just follows read().  I think it started giving
> the behaviour that you don't want when I fixed read().

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.

Andrey A. Chernov

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to