horst wrote:
<snip>>
b) cron jobs that come with packages (log analysis/rotation, backup,...)
have the tendency to start at the hour, or 15/30/45 min. You don't want
to interfere with those, or compete for resources. Secondly, if your
cron job starts at 5:37, and some odd issues also start at 5:37 it's
easier to pip-point trouble spots.
In short, it pays off to schedule cron jobs wisely................Horst
It's so funny you mention 5:37 as an example time... At one point I had
a cron job scheduled at 5:37 and for some reason it (usually) wouldn't
run or complete... changing to 5:34 solved the problem (at least well
enough)...
Never did find out what the heck the conflict was....
Matthew S. Jarvis
IT Manager
Bike Friday - "Performance that Packs."
www.bikefriday.com
541/687-0487 x140
[EMAIL PROTECTED]
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
