9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] some shell scripts
Date: Thu, 14 Oct 2004 17:25:45 -0700	[thread overview]
Message-ID: <51866f86da16fb592ccf52a3223ef4de@collyer.net> (raw)
In-Reply-To: <416E9B72.9030400@9fs.org>

One could start lnfs early in cpurc and termrc, have it post a /srv
file, and have /lib/namespace* mount that /srv file.  I think that for
the sort of thing you described (with Beagle), creations and removals
are of primary interest, though one could watch for writes too.
Keeping a database or log of such changes (perhaps served from the
watcher file server, permitting some in-memory caching) is vastly
cheaper than statting a potentially huge set of files every second
(though the difference would be even bigger on (l)unix, with the
directory entries separated from the i-nodes).  One should be able to
just note the new file name, size and perhaps mtime of each write, so
the volume of data should be tolerable.  If you're building indices, a
watcher client would probably want to wait for a given file to be
closed and perhaps wait a little longer in case it's rewritten, then
index it.  Maybe index every changed file each hour, or something of
the sort.

I don't think the need kernel mods for this.



  reply	other threads:[~2004-10-15  0:25 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
2004-10-15  0:25       ` geoff [this message]
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=51866f86da16fb592ccf52a3223ef4de@collyer.net \
    --to=geoff@collyer.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).