From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ORCLOSE
Date: Mon, 3 Apr 2006 20:08:58 -0500 [thread overview]
Message-ID: <5d457b13215e1d6e20e08f2858df07a2@swtch.com> (raw)
In-Reply-To: <f13ef5b3ddbb46eecc6c62b40bae0a4f@quanstro.net>
> that's often not a reliable sign. networks go down. dhcp and
> ppp may reassign addresses.
Sorry. 9P does not address such concerns. There is no notion
of re-establishing a connection. If your connection is dropped,
your ORCLOSE files get removed, all your other files get closed
(including lock files, making them available for use by others).
If you are concerned about keeping a single 9P session across
multiple network instances, you can use a 9P filter like aan or
recover. Aan just sits on top of any network connection, allowing
special clients and servers to reconnect and pick up where they
left off. Neither side knows that the connection got lost.
Recover is a client-only solution. A program runs on the client
that keeps track of the fids the client is using. If the connection
is lost, then recover redials and reestablishes the fid state as
needed. It handles ORCLOSE specially: it strips that bit out of the
open mode and turns Tclunks on previously-ORCLOSE fids into
Tremoves. It also refuses to reopen exclusive-use files.
Recover is not in the distribution yet. I wrote it for the old 9P and
revised it for 9P2000 but never quite finished it. Gorka finished it
and tested it last summer but I haven't gotten around to putting
it in. So for now it's ozinferno^Wvapor-ware. Sorry.
Russ
next prev parent reply other threads:[~2006-04-04 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 23:42 erik quanstrom
2006-04-04 1:08 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 23:10 erik quanstrom
2006-04-03 15:11 Fco. J. Ballesteros
2006-04-04 0:40 ` 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=5d457b13215e1d6e20e08f2858df07a2@swtch.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).