From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lnfs
Date: Wed, 2 Oct 2002 05:29:20 +0100 [thread overview]
Message-ID: <0a43e7dfd43830d10a2ceff45a562456@9fs.org> (raw)
> I'm not sure what you mean by flush, fprint is synchronous.
> I could retry the write if you like, though there's not
> much likelyhood that it would work the second time if
> it didn't the first, there's no lock on .longnames,
> it's append only, so a failure is probably the fs or
> someone having removed the file.
>
> .longnames is also written before the file is created,
> so the name should be there should you find the hashed
> file when reading the dir.
>
I stupidly thought the open could fail if someone else had
it open.
> 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...
On another tack, how do I set up /lib/ndb/local so that
mail to a particular site (vitanuova.com) is sent to a particular
machine, in preference to what the public dns says?
I tried
dom=vitanuova.com mx=wibble pref=10
but it doesn't show up in ndb/dnsquery.
next reply other threads:[~2002-10-02 4:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 4:29 nigel [this message]
2002-10-02 13:22 ` david presotto
-- strict thread matches above, loose matches on Subject: below --
2002-10-02 7:05 Geoff Collyer
2002-10-02 5:08 Russ Cox
2002-10-02 13:15 ` 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=0a43e7dfd43830d10a2ceff45a562456@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).