From: David Bremner <david@tethera.net>
To: "J. Lewis Muir" <jlmuir@imca-cat.org>,
Austin Clements <aclements@csail.mit.edu>
Cc: notmuch@notmuchmail.org, Paul Wise <pabs@debian.org>
Subject: Re: [Paul Wise] Bug#843127: notmuch: race condition in `notmuch new`?
Date: Mon, 14 Nov 2016 14:59:06 -0400 [thread overview]
Message-ID: <877f85nb0l.fsf@tesseract.cs.unb.ca> (raw)
In-Reply-To: <20161114184402.GB23082@tuna.imca.aps.anl.gov>
"J. Lewis Muir" <jlmuir@imca-cat.org> writes:
> On 11/12, Austin Clements wrote:
>> Quoth David Bremner on Nov 04 at 1:26 pm:
>> > I agree it looks like a race condition. inotify sounds a bit
>> > overcomplicated and perhaps non-portable? It should probably just
>> > tolerate disappearing files better, consider that a warning.
>>
>> Inotify really *is* the solution.
>
> I don't see how inotify can be the solution unless the idea is to make
> Notmuch run on Linux only. Inotify is a Linux kernel API. Some other
> OSes have their own native file event notification facilities, but not
> all of them have it, and most (if not all) only support file event
> notifications for certain file systems and not for others (e.g., not for
> NFS).
Yeah, it's worth saying that, even if I think Austin knows. I was
thinking that an alternative approach might be to have either notmuch
new or notmuch insert take a file name on the command line, and let the
user call it via what ever kind of directory watcher utility works on
their system.
d
next prev parent reply other threads:[~2016-11-14 18:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 12:46 [Paul Wise] Bug#843127: notmuch: race condition in `notmuch new`? David Bremner
2016-11-04 16:26 ` David Bremner
2016-11-13 1:51 ` Austin Clements
2016-11-14 18:44 ` J. Lewis Muir
2016-11-14 18:59 ` David Bremner [this message]
2016-11-04 18:47 ` Jani Nikula
2016-11-05 2:15 ` Paul Wise
2016-11-05 12:57 ` [PATCH] cli: consider files vanishing during notmuch new non-fatal Jani Nikula
2016-11-05 13:22 ` Paul Wise
2016-11-12 15:39 ` David Bremner
2016-11-12 16:04 ` Brian Sniffen
2016-11-12 16:10 ` David Bremner
2016-11-12 16:15 ` David Bremner
2016-11-12 21:08 ` Brian Sniffen
2016-11-12 21:36 ` David Bremner
2016-11-12 20:35 ` Jani Nikula
2016-11-16 11:43 ` David Bremner
2016-11-21 20:14 ` [PATCH v2] " Jani Nikula
2016-11-26 2:44 ` [PATCH] cli/new: document new exit code David Bremner
2016-11-26 9:17 ` Jani Nikula
2016-11-26 9:18 ` [PATCH] test: check the handling of files vanishing between scandir and indexing Jani Nikula
2016-11-27 9:59 ` [PATCH v2] " Jani Nikula
2016-11-29 2:16 ` David Bremner
2016-11-29 7:31 ` Tomi Ollila
2016-12-03 11:24 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877f85nb0l.fsf@tesseract.cs.unb.ca \
--to=david@tethera.net \
--cc=aclements@csail.mit.edu \
--cc=jlmuir@imca-cat.org \
--cc=notmuch@notmuchmail.org \
--cc=pabs@debian.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).