From: Chris Ball <cjb@mrao.cam.ac.uk>
To: jonathan@jonmasters.org
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [OT] inotify hack for locate
Date: Sun, 05 Mar 2006 23:41:49 +0000 [thread overview]
Message-ID: <yd3bqwkbgsi.fsf@islay.ra.phy.cam.ac.uk> (raw)
In-Reply-To: <35fb2e590603051336t5d8d7e93i986109bc16a8ec38@mail.gmail.com> (Jon Masters's message of "Sun, 5 Mar 2006 21:36:19 +0000")
>> On 5 Mar 2006 21:36:19, Jon Masters <jonmasters@gmail.com> said:
> I'm fed up with those finds running whenever I power on. Has
> anyone written an equivalent of the Microsoft indexing service to
> update locate's database?
I think the reason this hasn't been done is that inotify_add_watch()es
are non-recursive: you'd need a watch over every directory, and you'd
need a crawling step (churn, churn) to enumerate the directories to
add watches for.
Beagle (which only indexes home directories, by default) uses an
algorithm for placing watches as it crawls, such that by the end
of the crawl you can guarantee not to have a lost a race on new
directories being created while the crawl was happening:
http://mail.gnome.org/archives/dashboard-hackers/2004-October/msg00022.html
- Chris.
--
Chris Ball <cjb@mrao.cam.ac.uk> <http://www.mrao.cam.ac.uk/~cjb/>
next prev parent reply other threads:[~2006-03-05 23:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 21:36 Jon Masters
2006-03-05 21:42 ` Jesper Juhl
2006-03-05 21:50 ` Jon Masters
2006-03-06 9:23 ` Helge Hafting
2006-03-06 21:59 ` Pavel Machek
2006-03-05 21:53 ` Robin Holt
2006-03-05 22:02 ` Jon Masters
2006-03-05 21:43 ` Lee Revell
2006-03-05 23:08 ` Benjamin LaHaise
2006-03-05 23:30 ` Måns Rullgård
2006-03-06 21:53 ` Pavel Machek
2006-03-06 22:08 ` Måns Rullgård
2006-03-06 22:22 ` Pavel Machek
2006-03-08 13:56 ` Jan Engelhardt
2006-03-05 23:41 ` Chris Ball [this message]
2006-03-06 1:04 ` Jon Masters
2006-03-06 9:31 ` Helge Hafting
2006-03-06 13:10 ` Jon Masters
2006-03-07 0:11 ` Lee Revell
2006-03-07 0:33 ` Jon Masters
2006-03-07 10:26 ` Steven Rostedt
2006-03-09 2:44 ` Jon Masters
2006-03-06 7:49 ` Arjan van de Ven
2006-03-06 13:12 ` Jon Masters
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=yd3bqwkbgsi.fsf@islay.ra.phy.cam.ac.uk \
--to=cjb@mrao.cam.ac.uk \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®