#54 Ensuring That System cron Jobs Are Run
Until recently, Unix systems were all designed and developed to run as servers, up 24 hours a day, 7 days a week, forever. You can see that implicit expectation in the design of the cron facility: There's no point in scheduling jobs for 2:17am every Thursday if the system is shut down at 6pm for the night.
Yet many modern Unix and Linux users do shut down their systems at the end of the day and start it back up the following morning. It's quite alien to Mac OS X users, for example, to leave their systems running overnight, let alone over a weekend or holiday period.
This isn't a big deal with user crontab entries, because those that don't run due to actual shutdown schedules can be tweaked to ensure ...
Get Wicked Cool Shell Scripts now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
