Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Feb 2002 17:11:52 -0800
From:      "Crist J. Clark" <cristjc@earthlink.net>
To:        Joe & Fhe Barbish <barbish@a1poweruser.com>
Cc:        mpd <mpd6334@cs.rit.edu>, FBSD <freebsd-questions@FreeBSD.ORG>
Subject:   Re: Locate command
Message-ID:  <20020204171152.F3722@gohan.cjclark.org>
In-Reply-To: <LPBBIGIAAKKEOEJOLEGOAEJJCGAA.barbish@a1poweruser.com>; from barbish@a1poweruser.com on Mon, Feb 04, 2002 at 06:09:30PM -0500
References:  <20020204170456.A97655@rochester.rr.com> <LPBBIGIAAKKEOEJOLEGOAEJJCGAA.barbish@a1poweruser.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 04, 2002 at 06:09:30PM -0500, Joe & Fhe Barbish wrote:
> I edited the /etc/locate.rc file and uncommented the two
> statements you pointed out.
> Rebuilt locate DB using  sh /etc/periodic/weekly/310.locate
> It still did not pick up the non public files such as
> /usr/local/frontpage/version5.0/apache-fp/_vti_bin/fpexe,
> locate finds fpexe.c but not fpexe.

The commands to build the locate database are run as the user
'nobody.' If 'nobody' cannot read a directory, nothing below it will
find its way into the database. You can edit
/etc/periodic/weekly/310.locate to have it run as a different user,
but if you want the world to know the files are there, why not make
the directories world readable in the first place?

> If the locate does not load all files on the FBSD slice into
> the locate database is there some other command which will
> tell me where all copies of a file are located?

You can always try find(1).
-- 
Crist J. Clark                     |     cjclark@alum.mit.edu
                                   |     cjclark@jhu.edu
http://people.freebsd.org/~cjc/    |     cjc@freebsd.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020204171152.F3722>