The SUSE "run-crons" script is what runs the scripts in cron.hourly, cron.daily, etc. It runs each script in order, and doesn't run the next one until the previous one finishes. So, what I did was put a script named "00randomdelay" in each of the directories with this content:
#!/bin/sh # Delay a random amount of time before running # For weekly run, delay up to 1 hour sleep $((RANDOM%3600)) exit 0 The delay time is different for each directory. This way, the load is automatically spread out without making a unique customization to each server that I clone. Also, I moved a few of the scripts from cron.daily to cron.weekly so that they don't run as often. On 9/1/06, James Melin <[EMAIL PROTECTED]> wrote:
Well the first step was to spread things around time wise so everything is not happening at once. I'm going to see what that produces as far as change goes. But I see something called suse.de-check-battery that I'm pretty sure doesn't need to execute on a daily basis, or at all for that matter. But I will tend to those things after I'm back on the 11th. Thanks for the various insights gang. Much appreciated.
-- Bruce Hayden IBM Global Technology Services, System z Linux Endicott, NY ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
