At 06:39 PM 12/6/2000 -0600, you wrote:
>Let me guess: you shut your machine off at night?
Nope, it's on 24/7. Perhaps cron is broken.....
>locate uses a database that it rebuilds periodically, usually via a process
>called from cron. If your machine isn't on at 4am or whenever that process is
>scheduled, the database will not be updated. since locate doesn't access the
>filesystem directly, over time the database will be increasingly inaccurate.
>
>To fix this, either leave your machine on all the time, and if this doesn't fix
>the problem look at your systems crontabs and/or log files for clues as to why;
>
>or
>
>As root, manually run the "updatedb" command. That will take a while, as it
>scans all (or most) of your filesystem and rewrites the slocate database.
>
>HTH,
>-m
>
>Jonathan Wilson wrote:
>>
>> Whenever I look for something that locate doesn't think it can find I get the
>following error:
>>
>> locate: warning: database /var/lib/slocate/slocate.db' is more than 8 days old
>>
>> What's up with that?
>>
>> JW
>>
>> _______________________________________________
>> Redhat-list mailing list
>> [EMAIL PROTECTED]
>> https://listman.redhat.com/mailman/listinfo/redhat-list
>
>--
>Michael Jinks, IB // Technical Entity // Saecos Corporation
>"No one speaks English and everything's broken." -- T. Waits
>"Tom Waits would have made a decent sysadmin." -- M. Jinks
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
