On Tue, Jul 26, 2005 at 03:12:10PM +0200, Goswin von Brederlow wrote: > Nothing garanties that cron jobs are run at the right time. Running > it a bit later (whenever you boot) is just like it being delayed due > to excess load. If there are things that shouldn't be run at the wrong > time we should find them and protect them in the job itself.
Running a job a little later is not a problem. Running a job during work hours when it was scheduled to run during the night _is_ a problem since such jobs can (and usually do) hog both memory and I/O bandwidth, making interactive work difficult. In such cases not running the job for a day or two is way better than running it at a time it was not meant to run; not because it causes damage but because it causes real user inconvenience. Gabor -- --------------------------------------------------------- MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences --------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]