Download "Beyond Cron: How to Know When You've Outgrown Cron Scheduling--and What to Do Next"

USE OF INFORMATION: The information you provide may be used by Linux Journal and the content sponsor to send you information about their products and special promotions, but will otherwise not be released to third parties. If you do not wish to receive information from Linux Journal and/or sponsors, please e-mail publisher@linuxjournal.com.

For additional information about Linux Journal's privacy policy, go to http://www.linuxjournal.com/content/privacy-statement.

If you've spent any time around UNIX, you've no doubt learned to use and appreciate cron, the ubiquitous job scheduler that comes with almost every version of UNIX that exists. Cron is simple and easy to use, and most important, it just works. It sure beats having to remember to run your backups by hand, for example.

But cron does have its limits. Today's enterprises are larger, more interdependent, and more interconnected than ever before, and cron just hasn't kept up. These days, virtual servers can spring into existence on demand. There are accounting jobs that have to run after billing jobs have completed, but before the backups run. And, there are enterprises that connect Web servers, databases, and file servers. These enterprises may be in one server room, or they may span several data centers.