From: Sascha Retzki <sretzki@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] clunk clunk
Date: Tue, 3 Jan 2006 20:38:26 +0100 [thread overview]
Message-ID: <20060103193826.GA502@routi.local.net> (raw)
In-Reply-To: <775b8d190601031128t6efe9166ta02fad0dcf0f1d04@mail.gmail.com>
On Wed, Jan 04, 2006 at 06:28:48AM +1100, Bruce Ellis wrote:
> When a process exits it closes it's fds, so it sends a
> Tclunk ...but if the process it sends it to is exiting it can't
> respond. It's in the same position. Call it "deadly embrace".
Definitely not a nice situation. But from my (oh $god knows) limited
understanding of the great picture, when does that happen? File server
shutdowns? Wouldn't it be much nicer to make a "don't accept new
connections, wait X seconds for the clients to clunk, if time is over,
just clunk"-function. No other situations, none that I could think of,
would result in the situation you described.
> There is no close() in Inferno so the garbage collector is responsible.
I don't know limbo well, but I don't know how it could work without
close() in any way. Else see my rave above.
next prev parent reply other threads:[~2006-01-03 19:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 19:28 Bruce Ellis
2006-01-03 19:38 ` Sascha Retzki [this message]
2006-01-03 19:46 ` Russ Cox
2006-01-03 20:07 ` Bruce Ellis
2006-01-03 20:24 ` Russ Cox
2006-01-03 21:33 ` Bruce Ellis
2006-01-03 21:47 ` jmk
2006-01-03 22:09 ` Bruce Ellis
2006-01-03 22:14 ` jmk
2006-01-03 22:16 ` Bruce Ellis
2006-01-03 22:36 ` Russ Cox
2006-01-03 22:45 ` Bruce Ellis
2006-01-04 12:15 ` Russ Cox
2006-01-04 12:25 ` Bruce Ellis
2006-01-04 15:36 ` Ronald G Minnich
2006-01-04 15:41 ` Bruce Ellis
2006-01-05 9:36 ` Francisco J Ballesteros
2006-01-05 9:39 ` Russ Cox
2006-01-05 12:00 ` Bruce Ellis
2006-01-05 12:36 ` Charles Forsyth
2006-01-05 15:26 ` Francisco J Ballesteros
2006-01-06 21:34 ` Dave Eckhardt
2006-01-06 21:57 ` Bruce Ellis
2006-01-06 22:00 ` Francisco J Ballesteros
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=20060103193826.GA502@routi.local.net \
--to=sretzki@gmx.de \
--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).