[lug] slocate.db.stf

Ben bluey at iguanaworks.net
Thu Dec 28 19:04:10 MST 2006


On Thu, 2006-12-28 at 18:03 -0700, David L. Anselmi wrote:
> Hugh Brown wrote:
> > 
> > On Thu, 28 Dec 2006, Ben wrote:
> [...]
> >> Ok, so a duplicate cron entry sounds like reasonable cause.
> [...]
> > Another possibility is that updatedb is running so slowly that another one
> > gets fired off before the previous one is finished.
> 
> All the crons that run get logged in syslog.  Did you look there?
> 

Maybe its a debian thing, but syslog just logs that CRON started
cron.daily (and other items in crontab) but it doesn't individualize the
items under cron.daily. 

I'll take Hugh's suggestion and log start and stop times for
running /etc/cron.daily/slocate. Hopefully that'll give a clue.


Thanks,

Ben



> Dave
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug




More information about the LUG mailing list