From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Interrupting select
Date: Thu, 3 May 2001 01:44:35 +0200 (MET DST) [thread overview]
Message-ID: <200105022344.f42NiZ727894@oboe.it.uc3m.es> (raw)
"Mark Hahn wrote:"
> > while (1) {
> > int res = select(n,rfds,wfds,efds,&timeout);
> > if (res > 0)
> > return res; // data or error is expected
> > if (res == 0) {
> > return -ETIME; // timeo in select
> > }
> > }
> >
> > A resounding "no". kill -9 hurts it but it's invulnerable to everything
> > else.
>
> um, shouldn't you be testing for res==-1, as well?
> specifically that condition and errno==EINTR is how I'd expect
> signals to effect the loop...
Possibly .. if so that's the answer. But the man page doesn't say so:
tained in the descriptor sets, which may be zero if the
timeout expires before anything interesting happens. On
error, -1 is returned, and errno is set appropriately;
I assumed that "error" is something like trying to watch for a
negative number or zero descriptors, or having a fd_set that doesn't
contain open fd's. The reason I assumed that is because EINTR is not
listed as a possible:
ERRORS
EBADF An invalid file descriptor was given in one of the
sets.
EINTR A non blocked signal was caught.
EINVAL n is negative.
ENOMEM select was unable to allocate memory for internal
tables.
But I'm willing to give it a try! Thanks!
Now back to your regularly scheduled programs ...
Peter
next reply other threads:[~2001-05-02 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 23:44 Peter T. Breuer [this message]
2001-05-06 16:44 ` Stephen Wille Padnos
-- strict thread matches above, loose matches on Subject: below --
2001-05-02 21:46 Laramie Leavitt
2001-05-02 21:56 ` Peter T. Breuer
2001-05-02 22:21 ` Alan Cox
2001-05-02 23:03 ` Peter T. Breuer
2001-05-03 0:01 ` Alan Cox
2001-05-04 20:59 ` Olaf Dietsche
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=200105022344.f42NiZ727894@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--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®