From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] double trouble
Date: Wed, 10 Dec 2003 09:32:10 -0500 [thread overview]
Message-ID: <f963fbaacf08033cfd815c0a73536609@plan9.bell-labs.com> (raw)
In-Reply-To: <E1AU58Z-000CsS-2e@t40.swtch.com>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
A dichotomy twixt tools that shouldn't be there. It looks like upas/fs always locks
L.mbox but that upas/deliver and upas/send lock the file L.(basename of mailbox being used).
Usually, they're the same but if we're delivering into other mailboxes, they aren't.
I'll make everything lock /mail/box/<user>/L.mbox and avoid the problem all together.
I'll run it locally for a while since I'm sure to generate at least one deadlock
along the way.
[-- Attachment #2: Type: message/rfc822, Size: 2531 bytes --]
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] double trouble
Date: Wed, 10 Dec 2003 09:16:20 -0500
Message-ID: <E1AU58Z-000CsS-2e@t40.swtch.com>
> The attached mail from 'caldo.demon.co.uk!forsyth'
> to 'plan9.bell-labs.com!9trouble' alias `local!9trouble'
> failed with error '/bin/upas/deliver: opening mailbox: permission denied'.
>
>
> the gist of the message (which i've resent to another address)
> was: if you use filterkit's pipeto with
> if(isspam)
> spool /mail/box/$USER/spam
> ensure chmod a+rw on /mail/box/$USER/L.spam
> or each delivery of spam will take a little time.
Note that this says L.spam and not L.mbox,
a fact that I completely missed on first few readings.
Russ
next prev parent reply other threads:[~2003-12-10 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 9:02 Charles Forsyth
2003-12-10 14:16 ` Russ Cox
2003-12-10 14:32 ` David Presotto [this message]
2003-12-10 16:52 ` Fco.J.Ballesteros
2003-12-11 1:08 ` boyd, rounin
2003-12-11 0:54 ` boyd, rounin
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=f963fbaacf08033cfd815c0a73536609@plan9.bell-labs.com \
--to=presotto@closedmind.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).