From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] thread confusion
Date: Wed, 21 Sep 2005 16:44:15 +0200 [thread overview]
Message-ID: <2e4165d0a4172357099de271ac66cd5e@lsub.org> (raw)
AFAIK, you must call threadnotify() to install a handler for your note.
If you don't do that, your process is killed (which is what you are
seeing right now).
You should probably install a handler that says 'it's ok, got the note'.
Use threadnotify to do this.
I understand that you are interested in the "side effect" of interrupting
the I/O call.
I't funny, anyway, because I had the same problem a few days ago;
I had to abort a connection to a `Broken-maybe' file server. I tried not
to use interrupts and I was nevertheless decided to
alarm(x)
read()
alarm(0)
the call. After letting Russ know, he (once more) suggested me not to
use interrupts and to read the Alef paper (which I had read before, btw).
However, after thinking it twice, I was able to avoid the interrupts.
(The process is kept there, it will sooner or later abort due to a broken
connection).
Thus, excuse me for suggesting this again ;-), have you tried not to use
interrupts? In your case, if "the other end" decides to give up, can't it
let you know so you could shutdown and restart in a clean way?
hth
next reply other threads:[~2005-09-21 14:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 14:44 Fco. J. Ballesteros [this message]
2005-09-21 15:05 ` Axel Belinfante
2005-09-21 15:42 ` Russ Cox
2005-09-21 20:25 ` Axel Belinfante
2005-09-21 20:32 ` Axel Belinfante
2005-09-21 20:37 ` Russ Cox
2005-09-21 22:34 ` Axel Belinfante
2005-09-21 22:44 ` Russ Cox
2005-09-26 18:40 ` rog
2005-09-26 18:52 ` Russ Cox
2005-09-26 19:20 ` rog
2005-09-27 10:12 ` Axel Belinfante
-- strict thread matches above, loose matches on Subject: below --
2005-09-21 15:48 Fco. J. Ballesteros
2005-09-21 13:53 Fco. J. Ballesteros
2005-09-21 14:32 ` Axel Belinfante
2005-09-21 13:25 Axel Belinfante
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=2e4165d0a4172357099de271ac66cd5e@lsub.org \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).