From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <27736ad981afb1e6336f221492208ffa@lsub.org>
To: 9fans@cse.psu.edu
From: "Fco. J. Ballesteros" <nemo@lsub.org>
Date: Mon,  3 Apr 2006 17:11:21 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] ORCLOSE
Topicbox-Message-UUID: 2d26ca58-ead1-11e9-9d60-3106f5b1d025

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. 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.

My question is, whouldn't it be better to honor ORCLOSE
within the file server? (i.e., lib9p and fossil, mostly).
This is more resilient to failures and disconnections of the
client kernel. Otherwise, files are kept hanging around.

I was about to change this for Plan B, because we use
ORCLOSE files to announce our file trees. If this is no ok
for Plan 9 as well, I'll use something else for our announces.

thanks