From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <edb7aacb0634221947b32b8adbb9a7cd@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ORCLOSE
From: "Russ Cox" <rsc@swtch.com>
Date: Mon,  3 Apr 2006 19:40:55 -0500
In-Reply-To: <27736ad981afb1e6336f221492208ffa@lsub.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 2e221502-ead1-11e9-9d60-3106f5b1d025

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