Xref: utzoo comp.sys.hp:6120 comp.unix.internals:162
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.sys.hp,comp.unix.internals
Subject: Re: hp-ux 7.0/800 select() strangeness?
Message-ID: <11018:Sep910:17:0290@kramden.acf.nyu.edu>
Date: 9 Sep 90 10:17:02 GMT
References: <CPH.90Sep6054007@kleph.ai.mit.edu> <1990Sep6.172144.18775@dg-rtp.dg.com> <CPH.90Sep9022935@kleph.ai.mit.edu>
Organization: IR
Lines: 14

In article <CPH.90Sep9022935@kleph.ai.mit.edu> cph@zurich.ai.mit.edu (Chris Hanson) writes:
> The real problem here is that the documentation for `select' doesn't
> define what it does.  The documentation defines the results as "ready
> for reading, writing, or has an exceptional condition", but fails to
> say what that means.

That a read or write wouldn't block if the descriptor were blocking.
Exceptional conditions are defined by the device.

Since passing nonblocking descriptors to application programs is a
serious violation of convention, you shouldn't run into problems unless
you're creating them.

---Dan