I've always used locate by doing: sudo updatedb
locate *.ick This can cause problems though as it will trawl everyones files. updatedb sometimes takes a little while to run, but then locate is very quick afterwards. On 06/08/07, Jim Kissel <[EMAIL PROTECTED]> wrote: > > > Neil Greenwood wrote: > > On 06/08/07, Jim Kissel <[EMAIL PROTECTED]> wrote: > >> find /your/path/to/a/directory -name '*.lck' -print > >> > >> Find trawls the files system but appears to cache when re-run with a > >> short (hours) time. I've ever used locate. It has a db where it > >> 'locates' files. BTY, if you are using find on directories that you > >> don't "own", you may need to sudo find has the errors it produces when > >> it doesn't have permission to read a directory can overwhelm the actual > >> output of any search. > >> > > > > I'm posting without testing, so I may be wrong. > > > > I wouldn't have thought that find would cache the results. It's > > probably the disk cache for the file system that speeds things up. > > I too believe it the file system/disk that is doing the caching. Never > considered that anyone would splice a cache onto to find! > > > > Hwyl, > > Neil. > > > > -- > Simple effective migration to Open Source based computing > > Jim Kissel > Open Source Migrations Limited > w: http://www.osml.eu > e: [EMAIL PROTECTED] > p: +44(0) 8703 301044 > m: +44(0) 7976 411 679 > > -- > ubuntu-uk@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk > https://wiki.kubuntu.org/UKTeam/ > -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.kubuntu.org/UKTeam/
