From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ORCLOSE
Date: Mon, 3 Apr 2006 18:10:56 -0500 [thread overview]
Message-ID: <19e44c4bc4ea34bd15666846a952e9a0@quanstro.net> (raw)
how would the fs determine that the machine hosting the
client is in casters-up mode?
- erik
On Mon Apr 3 10:12:35 CDT 2006, nemo@lsub.org 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. 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
>
>
next reply other threads:[~2006-04-03 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 23:10 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 23:42 erik quanstrom
2006-04-04 1:08 ` Russ Cox
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=19e44c4bc4ea34bd15666846a952e9a0@quanstro.net \
--to=quanstro@quanstro.net \
--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).