At 11:27 AM 11/3/2008, you wrote: >On Nov 3, 2008, at 7:05 AM, Sebastian Kuzminsky wrote: > > > Mark Wendt (Contractor) wrote: > >> And though it's not a unixy question type list, for those unix noobs > >> that want or need to find a file that's located somewhere in the > >> system but you have no idea where, type "cd /", then "find . -name > >> <filename> -print". This command, with it's qualifiers, starts > >> looking in your current working directory, and recursively searches > >> through each subdirectory for the file in question. > > > > On a well-functioning Ubuntu system, you should be able to get much > > quicker results from "locate <filename>". > >However, locate runs off a database. Normally cron runs a job called >updatedb , maybe once a day, which does just that. >If you have a file that is too new to have hit the update then >manually run updatedb and then use locate. > >HTH > >Dave
Thanks Dave. I'll keep that in mind. I find I really like the locate command. I was playing around a bit with it yesterday. Accessing a database is certainly tons faster than having the "find" command recursively search through the entire system. It gets really slow when you have large NFS mounted disks too. Mark ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
