Try looking at the script file: /usr/sbin/run-crons
it is run every ten minutes by /etc/crontab and looks for things that haven't been done recently. Adjustment here may be necessary. An alternative may be to edit /etc/init.d/local so that it checks the time stamp on the database and updates it if it is x minutes old and not near the time of day that cron will do it. slocate should prevent itself from running twice. Another alternative is to edit /etc/crontab to change the time of day that the cron.daily scripts are run to 7:10am. On Fri, 2005-02-18 at 07:41 +0800, William Kenworthy wrote: > I am having problems with vixie-cron: My laptop is usually turned off > at night and cron.daily is set to run by the gentoo default at 03.01am. > Even if I start it up at 6am and let it sit for a couple of hours, it > picks up the missing cron job(s) sometime after 9am (not sure when > exactly). Where does gentoo set this timing so I can alter it. > > Its a real drag that updatedb, tripwire etc all startup (at the same > time). This will place it smack in the middle of regular presentations > using OO I will be giving over the next few weeks! At this time, the > laptop will be running on battery (this type of disk usage severely > reduces battery time - from ~1.75 hrs to ~1 hr) and speedstep drops the > clock from 2.2G to 1.2G (to increase battery time!) so there is even > less grunt to run OO. > > BillK > -- -- [email protected] mailing list
