From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] upas locking
Date: Thu, 18 Apr 2013 16:24:51 +0200 [thread overview]
Message-ID: <1A70F044-4B17-4D0F-AE80-2BA28F0D28D1@lsub.org> (raw)
In-Reply-To: <96ac8463d3e63c152de3bf159eb53fb6@kw.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
Yes, I noticed the comment, but I thought it was wrong.
The problem was that we had quite a number of upas/fs's and scanmails
running and it was because one of them had a problem and kept a
/mail/tmp/L.mbox file locked. All other ones kept waiting for that
(although all of them were using different "mboxes" created by the
piped script at /mail/tmp/$pid.blah.blah
Making this change made problems go away, and I didn't notice any
problem in imap so far. I guess I'll have to reread the imap source to see
if it really requires one lock per dir instead of one per mbox, but even so,
I think imap should use a different lock for that, it's upas/fs the one I'm
talking about.
thanks for the hint
On Apr 18, 2013, at 4:04 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> 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.
[-- Attachment #2: Type: text/html, Size: 4581 bytes --]
next prev parent reply other threads:[~2013-04-18 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 9:15 Francisco J Ballesteros
2013-04-18 14:04 ` erik quanstrom
2013-04-18 14:24 ` Francisco J Ballesteros [this message]
2013-04-18 14:42 ` erik quanstrom
2013-04-18 14:51 ` Fco. J. Ballesteros
2013-04-18 15:33 ` Charles Forsyth
2013-04-18 15:43 ` lucio
2013-04-18 15:59 ` Francisco J Ballesteros
2013-04-18 16:12 ` erik quanstrom
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=1A70F044-4B17-4D0F-AE80-2BA28F0D28D1@lsub.org \
--to=nemo@lsub.org \
--cc=9fans@9fans.net \
/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).