M
Meat Plow
Guest
On Thu, 06 Dec 2007 14:00:14 -0600, Moe Trin wrote:
> On Wed, 5 Dec 2007, in the Usenet newsgroup alt.os.linux.ubuntu, in article
> <1f3k5r.9k4.19.7@news.alt.net>, Meat Plow wrote:
>
>>Mark South wrote:
>
>>> find /etc -iname xorg.conf
>>
>>~$ slocate xorg.conf works too
>
> slocate (and the original 'locate') consult a database of files usually
> created as a nightly cron-job. If your system isn't running at the
> scheduled time, and you are not running a part-time cron daemon like
> anacron or fcron, then the database won't be up to date. Thus it will
> report about files you have deleted, and won't know about files that
> have been created or moved since that database update. The 'find'
> command looks to see what is "there" now, and tends to be much slower
> than reading a pre-existing database (that was created by running
> find as part of that cron-job).
>
> Find can be made to run faster by (as here) limiting the area of the
> filesystem that is searched. This implies that you are somewhat familiar
> with the way files are located. See http://tldp.org/guides.html and
> look through the 'Linux Filesystem Hierarchy' guide, which is a more
> user-friendly translation of the 'Filesystem Hierarchy Standard' which
> is available from http://www.pathname.com/fhs/.
>
> Old guy
That's fine and dandy if all your assumptions are correct.
> On Wed, 5 Dec 2007, in the Usenet newsgroup alt.os.linux.ubuntu, in article
> <1f3k5r.9k4.19.7@news.alt.net>, Meat Plow wrote:
>
>>Mark South wrote:
>
>>> find /etc -iname xorg.conf
>>
>>~$ slocate xorg.conf works too
>
> slocate (and the original 'locate') consult a database of files usually
> created as a nightly cron-job. If your system isn't running at the
> scheduled time, and you are not running a part-time cron daemon like
> anacron or fcron, then the database won't be up to date. Thus it will
> report about files you have deleted, and won't know about files that
> have been created or moved since that database update. The 'find'
> command looks to see what is "there" now, and tends to be much slower
> than reading a pre-existing database (that was created by running
> find as part of that cron-job).
>
> Find can be made to run faster by (as here) limiting the area of the
> filesystem that is searched. This implies that you are somewhat familiar
> with the way files are located. See http://tldp.org/guides.html and
> look through the 'Linux Filesystem Hierarchy' guide, which is a more
> user-friendly translation of the 'Filesystem Hierarchy Standard' which
> is available from http://www.pathname.com/fhs/.
>
> Old guy
That's fine and dandy if all your assumptions are correct.