There have been several reports of similar problems, most of which
appear to be associated with anacron, an occasional jobs schedular
similar to cron.
I had the problem myself on two boxes. Apparently one or more of the
scripts in /etc/cron.daily was bugging out when run under anacron --
though I have no clear understanding why this should be, as both anacron
and cron run "run-parts" with the same arguments.
Other symptoms you may want to check for are one or more hanging anacron
processes, and/or zombie processes related to your /etc/cron.daily
scripts.
The fix in my case was to remove the anacron package, as both the
affected systems are up 24/7. While cron will run the scripts in
/etc/cron.(daily|weekly|monthly), you may miss a cycle if your system is
down when the job would normally have run.
On Mon, Mar 27, 2000 at 03:10:35PM -0600, Bryan Walton wrote:
> Greetings,
> Today, I have noticed that when I do a locate on something, I get
> a warning message that locatedb is more than 8 days old. See the example:
> --cut--
>
> work:/home/walton# locate xf86config
> locate: warning: database `/var/lib/locate/locatedb' is more than 8 days
> old
> /usr/share/alien/patches/xf86config-glibc_1.0.0.i386-3.diff.gz
> /usr/X11R6/bin/xf86config
> /usr/X11R6/man/man1/xf86config.1x.gz
>
> --cut--
>
> Any ideas about what this means?
>
> Thanks,
> Bryan Walton
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
--
Karsten M. Self (kmself@ix.netcom.com)
What part of "Gestalt" don't you understand?
http://gestalt-system.sourceforge.net/
