From: Mike Castle <dalgoda@ix.netcom.com>
To: linux-kernel@vger.kernel.org
Subject: Re: select() - Linux vs. BSD
Date: Tue, 29 May 2001 10:34:47 -0700 [thread overview]
Message-ID: <20010529103446.B24802@thune.mrc-home.com> (raw)
In-Reply-To: <NDBBKBJHGFJMEMHPOPEGKEIICHAA.jcwren@jcwren.com>
On Tue, May 29, 2001 at 11:55:24AM -0400, John Chris Wren wrote:
> select will not be altered. In Linux, which claims BSD compliancy for this
> in the man page (but does not state either way what will happen to the
> bits), zeros the users bit masks when a timeout occurs. I have written a
Where in the man page does it state this? I just read it and couldn't find
any such statement.
I do, however, find the following:
exceptfds will be watched for exceptions. On exit, the
sets are modified in place to indicate which descriptors
actually changed status.
If there is a time out, it makes sense that no descriptors changed state,
and so everything would be zeroed out.
And actually, the example seems to support this:
if (retval)
printf("Data is available now.\n");
/* FD_ISSET(0, &rfds) will be true. */
The comment seems to indicate that if retval is 0, then FD_ISSET will be
false.
mrc
--
Mike Castle Life is like a clock: You can work constantly
dalgoda@ix.netcom.com and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
next prev parent reply other threads:[~2001-05-29 17:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 15:55 John Chris Wren
2001-05-29 17:34 ` Mike Castle [this message]
2001-05-29 19:51 ` Alan Cox
2001-05-29 20:50 ` lost
2001-05-29 21:06 ` dean gaudet
2001-05-31 1:40 ` Dr. Kelsey Hudson
2001-06-01 8:16 Andries.Brouwer
2001-06-01 16:38 ` lost
2001-06-02 21:46 ` Jamie Lokier
2001-06-03 2:13 ` lost
2001-06-01 17:33 Andries.Brouwer
2001-06-03 2:47 John Chris Wren
2001-06-03 3:31 ` Mike Castle
2001-06-03 7:52 ` David Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010529103446.B24802@thune.mrc-home.com \
--to=dalgoda@ix.netcom.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®