From: Jed Brown <jed@59A2.org>
To: Tassilo Horn <tassilo@member.fsf.org>,
Mikhail Gusarov <dottedmag@dottedmag.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Notmuch doesn't index new mails when mail location contains symlinks
Date: Mon, 23 Nov 2009 16:16:58 +0100 [thread overview]
Message-ID: <87tywl46fp.fsf@59A2.org> (raw)
In-Reply-To: <871vjpl1yi.fsf@thinkpad.tsdh.de>
On Mon, 23 Nov 2009 16:01:41 +0100, Tassilo Horn <tassilo@member.fsf.org> wrote:
> Tassilo Horn <tassilo@member.fsf.org> writes:
> I don't have to touch the symlinks or the directories inside the
> locations the symlinks point to, but instead I have to touch the
> top-level directory where the symlinks are contained in.
Ah, it's slightly more subtle. Notmuch correctly uses stat() instead of
lstat() to check whether the link target changed. However, mtime for
your mail root directory (containing the symlinks) does not get updated
when the target of the symlinks is updated. I think the only way to fix
this is to replace the current search (which skips a directory as soon
as it's mtime is older than the database) with one that enters all
directories so that symlinks are actually followed.
Jed
next prev parent reply other threads:[~2009-11-23 15:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 10:49 Notmuch doesn't index new mails Tassilo Horn
2009-11-23 13:55 ` Notmuch doesn't index new mails when mail location contains symlinks (was: Notmuch doesn't index new mails) Tassilo Horn
2009-11-23 14:02 ` Notmuch doesn't index new mails when mail location contains symlinks Mikhail Gusarov
2009-11-23 14:43 ` Tassilo Horn
2009-11-23 15:01 ` Tassilo Horn
2009-11-23 15:10 ` Mikhail Gusarov
2009-11-23 15:16 ` Jed Brown [this message]
2009-11-23 15:03 ` Jed Brown
2009-11-23 15:11 ` Mikhail Gusarov
2009-11-26 18:34 ` Carl Worth
2009-11-26 18:39 ` Jed Brown
2009-11-26 21:14 ` Carl Worth
2009-11-26 21:22 ` Jed Brown
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=87tywl46fp.fsf@59A2.org \
--to=jed@59a2.org \
--cc=dottedmag@dottedmag.net \
--cc=notmuch@notmuchmail.org \
--cc=tassilo@member.fsf.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).