On Sunday 16 Feb 2003 6:37 pm, Derek Jennings wrote: > On Sunday 16 Feb 2003 9:01 am, Anne Wilson wrote: > > On Sunday 16 Feb 2003 12:06 am, Derek Jennings wrote: > > > On Saturday 15 Feb 2003 2:56 pm, Anne Wilson wrote: > > > > I thought I had set up a cron job (using webmin) to update the > > > > database every night. Indeed, I thought I had seen indication that > > > > it had run, but today I have seen > > > > > > > > slocate: warning: database /var/lib/slocate/slocate.db' is more than > > > > 8 days old > > > > > > > > How can I find what went wrong? Could it be that I have set it as a > > > > user and it needs to be root? > > > > > > > > Anne > > > > > > Yes updatedb needs to be run as root. > > > > OK - I'll look into changing that. > > > > > Another potential problem is if your computer is switched off when the > > > job is due to run. Cron will not run jobs whose time has passed. The > > > solution is to install anacron which will check for missed jobs and run > > > them. > > > > I run 24/7 unless I'm away for a few days. > > > > > BTW: a cron job to run updatedb is already part of the cron.weekly job. > > > So your job should be unneccessary > > > > Which makes it even odder, that it should report as being more than 8 > > days old, doesn't it? > > > > Anne > > a possible reason for cron.weekly apparently not doing your updatedb is if > another part of the job is failing and causing the remainder to abort. > > If you enter a line > MAILTO=your_email_addy into /etc/crontab then any jobs which fail will > cause an email to be sent to you. > Thanks Derek - done that, now I'll wait to see what happens.
Anne -- Registered Linux User No.293302
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
