From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] waiting for dead procs with libthread
Date: Thu, 3 Nov 2005 13:18:07 -0500 [thread overview]
Message-ID: <ee9e417a0511031018g3b0d402fv589c65ef7932cca@mail.gmail.com> (raw)
In-Reply-To: <563aed238673db601799c8fde8499077@lsub.org>
> Your own procs can't do that either if they die. Right?
> Or perhaps the argument was that in that case it doesn't matter?
If one proc dies unexpectedly, your program is now in an
inconsistent state (maybe it was holding some locks;
maybe it was in the middle of editing some data
structure; etc.) and you are screwed anyway.
Russ
next prev parent reply other threads:[~2005-11-03 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 18:01 Fco. J. Ballesteros
2005-11-03 18:18 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-03 17:54 Fco. J. Ballesteros
2005-11-03 17:58 ` Russ Cox
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=ee9e417a0511031018g3b0d402fv589c65ef7932cca@mail.gmail.com \
--to=rsc@swtch.com \
--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).