From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lnfs
Date: Wed, 2 Oct 2002 01:08:03 -0400 [thread overview]
Message-ID: <9acf0838ced8becdebed4425da4af41f@plan9.bell-labs.com> (raw)
> > However, in rreaddir, I don't reread the file while
> > translating the short names to long ones. Someone
> > could create a file while I'm busy converting the
> > dir. There's plenty of window there for someone to
> > sneak through.
>
> I think this is the problem. I had a process running on the
> cpu server which walked the tree finding things to do, and
> another process on my terminal which added things to the
> tree. Perhaps I won't use lnfs after all...
Just put a readnames() call right after the dirreadall() call.
The race goes away, no?
Russ
next reply other threads:[~2002-10-02 5:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 5:08 Russ Cox [this message]
2002-10-02 13:15 ` david presotto
-- strict thread matches above, loose matches on Subject: below --
2002-10-02 7:05 Geoff Collyer
2002-10-02 4:29 nigel
2002-10-02 13:22 ` david presotto
2002-10-01 13:51 presotto
2002-10-01 8:18 nigel
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=9acf0838ced8becdebed4425da4af41f@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).