mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: jonathan@jonmasters.org
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OT] inotify hack for locate
Date: Mon, 06 Mar 2006 10:23:55 +0100	[thread overview]
Message-ID: <440BFFAB.2040405@aitel.hist.no> (raw)
In-Reply-To: <35fb2e590603051350o27a00274r4566e65e3fb99721@mail.gmail.com>

Jon Masters wrote:

>On 3/5/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
>
>  
>
>>On 3/5/06, Jon Masters <jonmasters@gmail.com> wrote:
>>    
>>
>
>  
>
>>>I'm fed up with those finds running whenever I power on.
>>>      
>>>
>
>  
>
>>You run updatedb at boot time?
>>    
>>
>
>No, but said box will catch up cron jobs on boot.
>
>  
>
>>Why not run it from cron at night like most people do?
>>    
>>
>
>That's not the point. It usually does. I'm interested to know if
>anyone has written a daemon that can sit and just do this
>synchronously on my desktop - then not only do I /not/ have to run
>updatedb every day but I can also have a locate that is always up to
>the minute.
>  
>
I haven't heard about anyone doing this.  You could modify
the VFS to notify you everytime a file is created, moved or deleted.
That should give you what you want, but at the cost of delaying
those operations.

Another option would be to make a filesystem that stores its
directory structure (or a copy of it) in a single file, so that
a locate-like program can do quick lookups of the always-correct
data.

Helge Hafting

  reply	other threads:[~2006-03-06  9:24 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 [this message]
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
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=440BFFAB.2040405@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=jesper.juhl@gmail.com \
    --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®