On Tue, Jul 09, 2002 at 12:22:33AM +0200, FACORAT Fabrice wrote:
> Le sam 06/07/2002 ? 14:15, Geoffrey Lee a ?crit :
>
> > And what are "these" things when I am only specifically talking about
> > slocated of course??
>
> slocate database rebuild
> rpm check ( the weirdnest )
>
actually rpm check isn't so bad only my system (~ 10 sec), compared to the
time slocate + msec_find took to run at 4 am (~ 6 min)
> when i had ide bus reset on hda ( my main hd where the sys where
> installed ). no more disk access, see proc I/O growing in gkrellm and
> then total freeze.
>
> > personally rebuilding the locate database less often is ok for me (like
> > FreeBSD)
>
> you're right
>
> but just a question : when will a win/desktop user will need this
> database ? I think that they are going to use graphical search tool. do
> they rely on locate/slocate ?
you mean the slocate database?
for me:
anytime you want to find a file, basically, unix books normally teach find
and people use that, but find may have to make you wait and also generate
disk activity:
glee@anakin local/src/linux-2.5.25 $ find . -name 'layout.h'
./fs/ntfs/layout.h
glee@anakin local/src/linux-2.5.25 $
(~ 8 sec)
and this is on a modern hard drive, now:
glee@anakin local/src/linux-2.5.25 $ locate -r '/layout.h$'
/usr/local/src/linux-2.5.25/fs/ntfs/layout.h
glee@anakin local/src/linux-2.5.25 $
personally I think it's a pity that no one ever uses it. I don't know if there
are any slocate gui, maybe someone should write one <shrug>.
-- Geoff.
