I can see your point, but it DOES generally take some time to search through 20 GB of files. However, you should only need to updatedb when you're looking for a file you just installed (since the last time cron ran). My solution to this has been to look carefully at the files I'm installing, including looking at the contents of .debs and .rpms and using `make -n install` (which prints the commands that would be run by `make install` without executing them).
HTH,
Levi
On Mon, 24 Feb 2003 20:59:26 -0500
Vernon <vsingleton@cfl.rr.com> wrote:
> Idiots like myself are tired of typing out "find / -name ..." and waiting.
> But rather, we like updatedb and locate, but find ourselves constantly
> typing
> "time updatedb" ... 2 minutes later ... "locate whatever",
> and because we are not even willing to wait 1+ minutes for the crontab
> we've even tried a little scripts like this:
>
> #!/bin/bash
> lockFile="/tmp/lock.${0#./}"
> echo $$ > $lockFile
> while [ -s $lockFile ]
> do
> updatedb
> sleep 1
> done
>
> but it boggs a system down noticably.
> Any ideas other than switching to BeOS?
>
> Vernon
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:42:56 EDT