From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] some shell scripts
Date: Thu, 14 Oct 2004 17:38:37 -0700 [thread overview]
Message-ID: <76ed6d4d107e23bfd0a8011cec3b4a14@collyer.net> (raw)
In-Reply-To: <ee9e417a04101417281dbec140@mail.gmail.com>
I guess I don't see how it fails to account for changes by others. If
you connect to a file server, you're either running its cpurc or
termrc (well, barring the case of cross-authentication-domain mounts)
or connecting to processes that run its /lib/namespace* files (e.g.,
drawterm).
Thinking about it some more, on a busy file server, you're probably
going to want to limit the volume of data you have to read to see the
changes to the files you care about, which suggests a watcher process
feeding each client only the changes they care about.
next prev parent reply other threads:[~2004-10-15 0:38 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
2004-10-15 0:28 ` Russ Cox
2004-10-15 0:38 ` geoff [this message]
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=76ed6d4d107e23bfd0a8011cec3b4a14@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).