begin  quote
On Fri, 7 Nov 2003 17:24:07 -0600
Steven Elling <ellings@kcnet.com> wrote:



> The reason I have this view is because I am a security aware
> individual.  I  set up slocate or updatedb so that it will not catalog
> files located in  /tmp, /usr/tmp, /var/tmp, /mnt, /root, /usr/src,
> /var/spool, and/home.  I also set users home directories to 0700.  In
> this scenario, running slocate  or updatedb daily is pointless, unless
> of course you update/install packages on your system every day.


I think that since you are an admin, and experienced at reconfiuring
slocate for your needs, makes you capable of moving or disabling the
cron jobs, so that shouldn't be an issue for you.



> 
> I didn't say slocate's purpose was for portage,  I was just saying
> that in  scenarios similar to mine it would be better to run or
> schedule slocate /   updatedb after a world or system update because
> that is the only time cataloged files would change.

Aye, perhaps. in cases like that I think its easier if you just hook
slocate to check the mtime on the counter file for portage, compare with
last time's and run if they differ.   Either that, or patch emerge to
fork a slocate after each time things are installed.


-- 
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end