1 Return-Path: <pioto@pioto.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id F3D55431FB6
\r
6 for <notmuch@notmuchmail.org>; Sat, 29 Jan 2011 08:10:09 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id sGZw3oQdw4YL for <notmuch@notmuchmail.org>;
\r
16 Sat, 29 Jan 2011 08:10:09 -0800 (PST)
\r
17 Received: from everglades.pioto.org (mail.pioto.org [207.192.71.235])
\r
18 by olra.theworths.org (Postfix) with ESMTP id A40B6431FB5
\r
19 for <notmuch@notmuchmail.org>; Sat, 29 Jan 2011 08:10:09 -0800 (PST)
\r
20 Received: from aether (c-68-44-60-100.hsd1.nj.comcast.net [68.44.60.100])
\r
21 (Authenticated sender: pioto)
\r
22 by everglades.pioto.org (Postfix) with ESMTPSA id 31BF8160644
\r
23 for <notmuch@notmuchmail.org>; Sat, 29 Jan 2011 11:10:09 -0500 (EST)
\r
24 Date: Sat, 29 Jan 2011 11:10:08 -0500
\r
25 From: Mike Kelly <pioto@pioto.org>
\r
26 To: notmuch@notmuchmail.org
\r
27 Subject: Re: notmuch's idea of concurrency / failing an invocation
\r
28 Message-ID: <20110129111008.1a09bbb6@aether>
\r
29 In-Reply-To: <AANLkTim9FEEn6bpeAb1oHVScs4RGbK-UrFY+52ZKWv4E@mail.gmail.com>
\r
30 References: <87fwsetdin.fsf@kepler.schwinge.homeip.net>
\r
31 <8762taxk9y.fsf@algae.riseup.net>
\r
32 <87vd1a84qj.fsf@servo.finestructure.net>
\r
33 <AANLkTi=pPgcPXUN_XTXa0gAkbTR_OF4XxCP-d4-Be2pt@mail.gmail.com>
\r
34 <87fwsdobpy.fsf@yoom.home.cworth.org>
\r
35 <877hdps6og.fsf@kepler.schwinge.homeip.net>
\r
36 <1296228975-ner-3626@everglades>
\r
37 <AANLkTim9FEEn6bpeAb1oHVScs4RGbK-UrFY+52ZKWv4E@mail.gmail.com>
\r
38 X-Mailer: Claws Mail 3.7.6 (GTK+ 2.22.1; x86_64-pc-linux-gnu)
\r
40 Content-Type: multipart/signed; micalg=PGP-SHA1;
\r
41 boundary="Sig_/rt5B5s1KAIDLrfcKTh_yLoj";
\r
42 protocol="application/pgp-signature"
\r
43 X-BeenThere: notmuch@notmuchmail.org
\r
44 X-Mailman-Version: 2.1.13
\r
46 List-Id: "Use and development of the notmuch mail system."
\r
47 <notmuch.notmuchmail.org>
\r
48 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
49 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
50 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
51 List-Post: <mailto:notmuch@notmuchmail.org>
\r
52 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
53 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
54 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
55 X-List-Received-Date: Sat, 29 Jan 2011 16:10:10 -0000
\r
57 --Sig_/rt5B5s1KAIDLrfcKTh_yLoj
\r
58 Content-Type: text/plain; charset=US-ASCII
\r
59 Content-Transfer-Encoding: quoted-printable
\r
61 On Fri, 28 Jan 2011 11:57:34 -0500
\r
62 Austin Clements <amdragon@mit.edu> wrote:
\r
64 > Yes, exactly. All of this. Unfortunately, Xapian doesn't expose the
\r
65 > ability to block on the lock (see the fcntl call in
\r
66 > backends/flint_lock.cc, which is hard-coded to the non-blocking
\r
67 > F_SETLK instead of F_SETLKW), so we'd either need a new Xapian
\r
68 > option, or we would just have to wrap our own flock/fcntl lock around
\r
69 > things as you suggest.
\r
71 Hrm. Do you know if Xapian upstream would be open to a patch to support
\r
72 optional blocking locks? We can't be the only ones hitting these sorts
\r
78 --Sig_/rt5B5s1KAIDLrfcKTh_yLoj
\r
79 Content-Type: application/pgp-signature; name=signature.asc
\r
80 Content-Disposition: attachment; filename=signature.asc
\r
82 -----BEGIN PGP SIGNATURE-----
\r
83 Version: GnuPG v2.0.17 (GNU/Linux)
\r
85 iEYEARECAAYFAk1EO+AACgkQokMzJ47YCzoKcACguce/PNy2kSO8kiGLaJH88yL3
\r
86 Z7YAn2ed8WCJhRto0n4MtzhrVCkqmd/0
\r
88 -----END PGP SIGNATURE-----
\r
90 --Sig_/rt5B5s1KAIDLrfcKTh_yLoj--
\r