> As I said the first time, updatedb.conf isn't used in casual use of
> updatedb. Look at the cron job:
>
> if [ -f /etc/updatedb.conf ]; then
> . /etc/updatedb.conf
> fi
>
> That '.' means that the contents of updatedb.conf are read and used to
> set environment variables. If you were doin
On Wed, Jul 18, 2001 at 01:27:09PM -0400, Mike Dresser wrote:
> router:~# locate \* | wc -l
> 68558
> router:~# updatedb
> router:~# locate \* | wc -l
> 91395
>
> Every night, updatedb runs, and updates, removing something like 21000
> files from the locatedb. Looking through the cron.daily, i se
On Wed, 18 Jul 2001, Colin Watson wrote:
> Mike Dresser <[EMAIL PROTECTED]> wrote:
> >router:~# locate \* | wc -l
> >68558
> >router:~# updatedb
> >router:~# locate \* | wc -l
> >91395
> >
> >Every night, updatedb runs, and updates, removing something like 21000
> >files from the locatedb.
>
> P
On Wed, 18 Jul 2001 at 15:19:06 -0400, Mike Dresser wrote:
[Please do *not* cc me on list mail. I read the list. Thanks.]
> On Wed, 18 Jul 2001, Colin Watson wrote:
> > Perhaps it's ignoring some of the paths and filesystems it's told to
> > prune in /etc/updatedb.conf? Those are only noticed by
Robert Waldner <[EMAIL PROTECTED]> writes:
> Well, there´s no point in making files only readable by specific users/
> groups if locate would locate them just nicely for everyone ;-)
Of course there is! They may be able to locate them, but they still
can't _read_ them.
Now, there may be cases
Mike Dresser <[EMAIL PROTECTED]> wrote:
>router:~# locate \* | wc -l
>68558
>router:~# updatedb
>router:~# locate \* | wc -l
>91395
>
>Every night, updatedb runs, and updates, removing something like 21000
>files from the locatedb.
Perhaps it's ignoring some of the paths and filesystems it's told
On Wed, 18 Jul 2001 13:27:09 EDT, Mike Dresser writes:
>Every night, updatedb runs, and updates, removing something like 21000
>files from the locatedb. Looking through the cron.daily, i see updatedb
>runs as nobody. Is there a particular danger in running this as other
>than nobody?
On multi-u
I believe there's a restricted locate, called slocate. Then again, it
looks like it's trying to do the same thing anyways, so that's what's
confusing me.
Fortunately, I have no shell users =)
On Wed, 18 Jul 2001, Robert Waldner wrote:
>
> On Wed, 18 Jul 2001 13:27:09 EDT, Mike Dresser writes:
>
router:~# locate \* | wc -l
68558
router:~# updatedb
router:~# locate \* | wc -l
91395
Every night, updatedb runs, and updates, removing something like 21000
files from the locatedb. Looking through the cron.daily, i see updatedb
runs as nobody. Is there a particular danger in running this as ot
9 matches
Mail list logo
