From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ORCLOSE
Date: Mon, 3 Apr 2006 19:40:55 -0500 [thread overview]
Message-ID: <edb7aacb0634221947b32b8adbb9a7cd@swtch.com> (raw)
In-Reply-To: <27736ad981afb1e6336f221492208ffa@lsub.org>
Nemo wrote:
> When a ORCLOSE file is created by a process at
> machine A into a FS at machine B, if the machine
> A goes away (e.g., you power it down), the file
> is not removed.
I believe this.
> This is as it could be expected, because
> ORCLOSE, IFAIK, is processed by the kernel during the cleanup
> done for the process while it exits.
But this is not true. ORCLOSE is processed by the remote server.
The kernel does not handle it specially when talking to a
remote 9P server. (It does handle ORCLOSE for local devices
like devenv and devsrv.)
I think what you are seeing is just a bug in fossil.
fidClunkAll should test for (fid->open & FidORclose) and
then do the remove. If you implement and test it I'd be
happy to see a patch.
Erik wrote:
> how would the fs determine that the machine hosting the
> client is in casters-up mode?
Loss of the TCP or IL connection is the usual sign.
Russ
next prev parent reply other threads:[~2006-04-04 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 15:11 Fco. J. Ballesteros
2006-04-04 0:40 ` Russ Cox [this message]
2006-04-03 23:10 erik quanstrom
2006-04-03 23:42 erik quanstrom
2006-04-04 1:08 ` 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=edb7aacb0634221947b32b8adbb9a7cd@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).