From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0a43e7dfd43830d10a2ceff45a562456@9fs.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lnfs
From: nigel@9fs.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Wed,  2 Oct 2002 05:29:20 +0100
Topicbox-Message-UUID: fad38060-eaca-11e9-9e20-41e7f4b1d025

> 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.