I see your point. (Note that the behavior you had implemented in term was
no better on this mark. There has never been a check on the peropen
modes.) From what I can see, on Linux and FreeBSD select and poll will
tell you all about the states you don't have access to. So they don't give
us muc
Roland McGrath <[EMAIL PROTECTED]> writes:
> I don't think that is what "invalid file descriptor" means in anything I
> have read. That is, things often say e.g. "an invalid file descriptor or a
> file descriptor not opened for reading". I have always interpreted
> "invalid file descriptor" to
> Well, the Linux manpage on my Debian system for select has:
Point one: Linux manpage. Ha. Ha ha.
>EBADF An invalid file descriptor was given in one of the
> sets.
>
> I interpreted that to include both a totally bogus number as well as
> one being used inappropriatel
Roland McGrath <[EMAIL PROTECTED]> writes:
> Why do you say that? I have never known of such behavior. Linux does not
> do it. FreeBSD does not do it. Those are the systems that it's handy for
> me to check right now, but I don't know of any reason to ever have
> suspected such a behavior. T
> > Log message:
> > 2001-05-26 Roland McGrath <[EMAIL PROTECTED]>
> >
> > * users.c (trivfs_S_io_select): Don't diagnose an error for *TYPE
> > containing irrelevant bits (i.e. SELECT_URG). It's always ok to
> > ask even when the answer is always no.
>
> I haven't looked
