On Monday 26 June 2006 22:41, Carlos E. R. wrote:
That's not what I said. I said to remove the flag file (0 bytes): /var/spool/cron/lastrun/cron.daily about one minute before the time you want updatedb to run, ie, at 1:59 am (you can do this with an "at" job or with a "cron" job). This way, when at 2:00 am the system cronjob runs, it sees the missing flag file and thinks that the updatedb has not run, and thus runs it inmediately. In fact, it will run then all the daily jobs, not only updatedb.
Useful info, Carlos - thanks. For the life of me I can't understand why there is this rat's nest of scripts, with such an unintuitive way to decide when they ought to be run - I thought one of the benefits of cron was supposed to be its simplicity, but this is hidden away here under multiple layers. The user is expected to work out that in order to run these tasks at a particular time, he has to set up a cronjob to delete a file that says they haven't been done yet??? It's logic, Jim, but not as we know it.... Why can't there be a page at install time, or a module in YaST, saying "Your PC will need to carry out some housekeeping tasks from time to time - select a time of the day when you would like these done"? I sometimes think the SUSE engineers believe it's cool to be obscure for the sake of it, and useability suffers. -- Pob hwyl / Best wishes Kevin Donnelly www.kyfieithu.co.uk - KDE yn Gymraeg www.eurfa.org.uk - Geiriadur rhydd i'r Gymraeg www.rhedadur.org.uk - Rhedeg berfau Cymraeg www.cymrux.org.uk - Linux Cymraeg ar un CD