From: Martin Steigerwald <Martin@lichtvoll.de>
To: nepomuk@kde.org
Cc: Jan Kara <jack@suse.cz>, John McCutchan <john@johnmccutchan.com>,
Robert Love <rlove@rlove.org>, Eric Paris <eparis@parisplace.org>,
Eric Paris <eparis@redhat.com>,
Linux Filesystem Development Mailinglist
<linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Nepomuk] Better support for (desktop) file search / indexing applications
Date: Thu, 1 Nov 2012 13:55:53 +0100 [thread overview]
Message-ID: <201211011355.54347.Martin@lichtvoll.de> (raw)
In-Reply-To: <201211011352.42476.Martin@lichtvoll.de>
Am Donnerstag, 1. November 2012 schrieb Martin Steigerwald:
> Furthermore there is an issue with updating the file index on login or
> service start. In order to catch all other file renames a indexer would
> have to run over every directory whose modification time stamp has
> changed again in order to see whether a (checksummed) file has moved.
>
> An approach like recursive mtime as proposed by Jan Kara can help to
> improve initial scan times a lot.
>
> As to what I know this scan has been enabled in Nepomuk recently, with
> the hope that files are moved mainly during the user session is
> active. I think thats an assumption that may be accurate for many
> cases.
disabled, not enabled.
I read over this before but did not see the typo.
Sorry,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2012-11-01 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 12:52 Better support for (desktop) file search / indexing applications Martin Steigerwald
2012-11-01 12:52 ` Martin Steigerwald
2012-11-01 12:55 ` Martin Steigerwald [this message]
2012-11-01 13:48 ` Tvrtko Ursulin
2012-11-10 16:53 ` Martin Steigerwald
2012-11-12 9:10 ` Tvrtko Ursulin
[not found] ` <CAKRKD_W8pW+8kUO2HvgCQrtqnHOZzgeGiwAF5ER3Yad4OMcizg@mail.gmail.com>
2013-03-10 4:51 ` Fwd: [Nepomuk] " Simeon Bird
2013-03-10 12:06 ` Lijo Antony
2013-03-12 2:55 ` Andreas Dilger
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=201211011355.54347.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=jack@suse.cz \
--cc=john@johnmccutchan.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nepomuk@kde.org \
--cc=rlove@rlove.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.