From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 18 Apr 2013 10:04:05 -0400
To: 9fans@9fans.net
Message-ID: <96ac8463d3e63c152de3bf159eb53fb6@kw.quanstro.net>
In-Reply-To: <7C2F640A-2A94-4AA1-9CE9-4E4845F0860F@lsub.org>
References: <7C2F640A-2A94-4AA1-9CE9-4E4845F0860F@lsub.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] upas locking
Topicbox-Message-UUID: 434e77e8-ead8-11e9-9d60-3106f5b1d025

> Looking into, we found that in upas/common/libsys.c the
> function generating the lock file name returns always "L.mbox"
> but not .../L.<mbox file name> as it seems it should.

i think the comment above the function is important
"we use one lock per directory".  it's been a long time since
i worked on nupas, so i don't recall all the details, but
iirc, imap4d relies on having one lock per directory.

of course, nupas takes pressure off the directory lock
by using mdir format, which doesn't require a lock.  the
indicies are lock files themselves.

under what circumstaces did you find a problem?

- erik