Re: [cobalt-users] Cobalt crontab question

["Steven Werby" <steven-lists@xxxxxxxxxxxx>]

Jeff Martin <jeff@xxxxxxxxxxxxxxxx> wrote:
> Why is the default cobalt crontab set up to run at odd times?  They appear
odd to me,
> because the daily dir is run at 4, the quarter-hourly is run 3,18,33,48.

Did you look at *all* of /etc/crontab.master (see output below)?  It looks
like Cobalt staggered the minutes after the hour at which the jobs run to
minimize the number of jobs being initiated at the same time.

> Must be a reason.

It doesn't look arbitrary.  Try changing all of the lines to run at 1 minute
after the hour and see if you have any problems.

# Run any at jobs every minute
* * * * * root [ -x /usr/sbin/atrun ] && /usr/sbin/atrun

# run-parts
03,18,33,48 * * * * root run-parts /etc/cron.quarter-hourly
04,34 * * * * root run-parts /etc/cron.half-hourly
01 * * * * root run-parts /etc/cron.hourly
05 0,6,12,18 * * * root run-parts /etc/cron.quarter-daily
02 1 * * * root run-parts /etc/cron.daily
02 2 * * 0 root run-parts /etc/cron.weekly
02 3 1 * * root run-parts /etc/cron.monthly

# Remove /tmp, /var/tmp files not accessed in 10 days (240 hours)
41 02 * * * root /usr/sbin/tmpwatch 24 /tmp /home/tmp /var/tmp
/var/cobalt/tmp

# Remove formatted man pages not accessed in 10 days
39 02 * * * root /usr/sbin/tmpwatch 240 /var/catman/cat?

# Monitor services to make sure everything is still okay.
0,15,30,45 * * * * root /usr/local/sbin/monitor

Steven Werby {steven-lists@xxxxxxxxxxxx}