From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sent source
Date: Thu, 07 May 2009 06:23:33 -0700 [thread overview]
Message-ID: <1241702060-sup-3211@entry> (raw)
In-Reply-To: <f96e0240905061702m43899549p5ea53b5b6c478b02@mail.gmail.com>
Reformatted excerpts from Ben Walton's message of 2009-05-06:
> The next option is to play with locks, but that's not straight forward
> at all.
This is my favorite option, because sup-sync-back also has to do mbox
locking, so I don't think we can avoid the issue in general.
> Dovecot, as an example, allows a configuration knob for the admin to
> set the order in which the different mechanisms are used. This works
> as long as all of the mbox consumers use the same sequence. There is
> still lots of room for error here (NFS, etc).
Currently sup-sync-back just says, "hey, you can use this program
/usr/bin/dotlockfile if you have it" and pushes the details of locking
to that. I think that's at least a vaguely reasonable approach. Ideally
it would be more configurable, would fall back to other locking
programs, etc., but I think it's significantly better than not doing any
locking at all.
(Eventually these two mbox writers should share the same locking code,
but don't feel obligated to refactor as part of your patch if it's
already getting too hairy.)
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-05-07 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 0:02 Ben Walton
2009-05-07 13:23 ` William Morgan [this message]
2009-05-07 21:57 ` Ben Walton
2009-05-09 2:10 ` Ben Walton
2009-05-09 13:01 ` William Morgan
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=1241702060-sup-3211@entry \
--to=wmorgan-sup@masanjin.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