From: "Thomas Kear" <thomas.kear@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?
Date: Fri, 21 Apr 2006 19:40:30 +1200 [thread overview]
Message-ID: <2b1fa7660604210040g132d66ecre087d1a4c694411b@mail.gmail.com> (raw)
In-Reply-To: <1145603382.15597.26.camel@omc-2.omesc.com>
I know it's not quite the answer you asked for, but might I suggest rlocate.
rlocate uses a kernel module to do real-time updates of the locate
database (uses very little cpu time), which as well as providing
instant indexing of new files reduces the complete hard drive trawl
from once a day to once a month.
http://rlocate.sf.net
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-21 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 7:09 [gentoo-user] What do I do about slocate 3.1/2.7 ? Jules Colding
2006-04-21 7:40 ` Thomas Kear [this message]
2006-04-21 15:44 ` Johám-Luís Miguéns Vila
2006-04-21 18:24 ` Richard Fish
2006-04-21 19:00 ` Johám-Luís Miguéns Vila
2006-04-21 21:27 ` Neil Bothwick
2006-04-22 8:20 ` Johám-Luís Miguéns Vila
2006-04-22 8:28 ` Mick
2006-04-22 14:37 ` [gentoo-user] " Jeff Grossman
2006-04-24 8:10 ` [gentoo-user] " Jules Colding
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=2b1fa7660604210040g132d66ecre087d1a4c694411b@mail.gmail.com \
--to=thomas.kear@gmail.com \
--cc=gentoo-user@lists.gentoo.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