From: Nigel Roles <nigel@9fs.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] some shell scripts
Date: Thu, 14 Oct 2004 16:29:54 +0100 [thread overview]
Message-ID: <416E9B72.9030400@9fs.org> (raw)
In-Reply-To: <2c09e36b136393b4df31b8b14a3c2f27@collyer.net>
geoff@collyer.net wrote:
>I think performance could be acceptable: I run lnfs over both file
>systems (main and other) on my old ken file server and it doesn't seem
>to slow things noticeably, and this should be similar: the file server
>would just pass requests through, taking note of creations and
>removals and updating its database. It sounds pretty straightforward
>actually.
>
>
>
I think you're right about the load implied by lnfs. You only need to
check the
.longnames file when opening or closing a file. This works with the lnfs
running
on the workstation and is therefore kenfs comaptible.
Surely for watching files, you want to know if other clients connected
to the fileserver
have changed things? Wouldn't this require a client to update a database
on every change
in case another client is interested in the changes it has made to a
particular
file?
This doesn't sound too different from simply statting every file you are
interested
in every second, which Martin reasonably suggested might be a little
heavyweight
when trying to build indexes for a large proportion of files on a file
system.
The bright new shiny inotify device in Linux (note it's a device so
accessibility over a
network might be a problem) sources events when inodes are updated and copes
with dismounts, which is attractive with so many hot-pluggable-widgets these
days. Within the system-centric Unix world, this is relatively tidy
compared to
SIGIO.
Seems like it might need some kenfs/fossil hacks for the Plan 9 world.
next prev parent reply other threads:[~2004-10-14 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 22:38 Russ Cox
2004-10-14 5:29 ` Martin C.Atkins
2004-10-14 6:50 ` geoff
2004-10-14 9:56 ` Martin C.Atkins
2004-10-14 15:29 ` Nigel Roles [this message]
2004-10-15 0:25 ` geoff
2004-10-15 0:28 ` Russ Cox
2004-10-15 0:38 ` geoff
2004-10-14 9:22 ` Fco. J. Ballesteros
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=416E9B72.9030400@9fs.org \
--to=nigel@9fs.org \
--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).