Le mar 09/07/2002 � 04:39, Geoffrey Lee a �crit : > 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)
oups I did it again ! I've forgot this one sad, but on my desktop I disable all msec/rpm/locate and whatever you want that increase my disk activity > > 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. and more I have the tips to sometimes make it work : knock the HD. sometimes I can hear when it decide to run again. it's not fuunny as this pb occur only one time obn win2k and several times on linux. > you mean the slocate database? yes > 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>. sure slocate is good i'm agree with as I used to use it. but we are talking in a desktop config. not for expert users ( they know how to activate/install slocate ), we are talking about normal users that avoid to use CLI and will use KDE find tool and so on ... so when will they use slocate ? maybe when they will ask to find a file on CLI ( seldom ), some will talk about find, and someone else about slocate. - slocate ? I don't have it ! - ok just install the rpm - how can I install slocate ? where is it ? - http://www.geekreview.org/slocate/ - apt-get locate :p - no he's a mandrake user and so : urpmi slocate. but take care you need the rebuild the db often because ... bla bla bla bla - ah ok thx question : does this man is going to use slocate again and take care about rebuilding the db ? i don't think. it will use slocate one time per month The GUI for slocate : http://alxobr.free.fr/xlocate/xlocate.html
