Learning Cron Job - History, Background & Why You Need It

#Introduction

In episode 0 we prepared the environment: bash, cronie, and an active crond. Now it's time to understand why cron exists — before we discuss how to use it. A tool whose history and philosophy you understand will be used wisely, not just copied from examples.

Cron is one of the oldest pieces of software still used every day. At nearly half a century old, it remains the backbone of server automation around the world. Understanding this journey also explains why there are so many variants: cronie, vixie-cron, anacron, and even systemd timers, which we'll cover in episode 18.

#History and Philosophy

#Born in Unix V7 (1975)

Cron was first written by Ken Thompson at AT&T Bell Labs, released as part of Unix V7 in 1975. It evolved from the more primitive scheduling system in Unix V1. The name cron comes from "chronos" — the god of time in Greek mythology. Its philosophy is simple: run commands at specific times without human interaction.

Thompson's original design used a per-user spool file — a pattern we still see in /var/spool/cron/ today.

#Vixie-Cron (1987)

In 1987, Paul Vixie rewrote cron from the ground up. Vixie-cron introduced the things we now consider standard:

The 5-field syntax we know (minute hour day month weekday).
The /etc/crontab file with a user field.
Support for the /etc/cron.d/ directory.
cron.allow and cron.deny for access control.

Vixie-cron became the de facto standard on BSD and many Linux distros for two decades.

#Cronie — the Active Fork (Default on RHEL/Fedora/Arch)

Vixie-cron was relatively stagnant, so the community created a fork called cronie, which is now the default scheduler on RHEL, Fedora, and Arch. The latest active version is 1.7.2. Cronie integrates anacron, improves email delivery (MAILFROM), and adds options like cron -n to wait for jobs to finish. We'll break down these features in episode 17.

#Anacron: for Non-24/7 Machines

Cron assumes the machine is always on. For laptops and workstations that often sleep, anacron was born — a program that runs missed jobs as soon as the machine comes back up. If a daily job was missed because the laptop was off at the scheduled time, anacron runs it at boot. Cronie bundles anacron so the two work together.

#Why You Need Cron

#Automating Routine Tasks Without Supervision

Imagine having to log in manually every night to back up a database, rotate logs, or clean up temporary files. That's not just boring — it's error-prone, especially at 03.00 AM. Cron removes the human dependency for work that is deterministic and routine.

The most common tasks automated with cron:

Backup — rsync, restic, or pg_dump during quiet hours.
Logrotate — rotating and compressing logs before the disk fills up.
Reports — generating daily reports and sending them out.
Cleanup — clearing /tmp, expired files, or job history.
Synchronization — periodically pulling data from external sources.

#Simple, Battle-Tested, and Universal

Cron is simple: one line in a text file, no dependencies, no extra daemon. It has been battle-tested in production for decades and is available on every Unix-like system — Linux, BSD, macOS — with the same syntax. This is why it has survived despite many modern alternatives appearing.

Tip

This timeline matters: Unix V7 (1975) gave birth to it, vixie-cron (1987) popularized the 5-field syntax, and cronie 1.7.2 is now the modern default. When reading distro documentation, distinguish what comes from vixie and what from cronie — the differences are small but real in options like -n.

#Quick Comparison: Cron Variants

To close out this episode, here's a map of the variants you'll often encounter:

Variant	Strengths	Weaknesses	Common on
vixie-cron	Stable, historic	Rarely updated	BSD, legacy distros
cronie 1.7.2	Active, integrated anacron	More complex configuration	RHEL, Fedora, Arch
anacron	Runs missed jobs	Not hour-precise	Non-24/7 machines
systemd timer	Dependencies, journal logging	Different syntax	All systemd distros

You'll learn to choose among them in episodes 8 and 18.

#Closing

Key takeaways:

Cron was born in Unix V7 (1975) by Ken Thompson, named after "chronos".
Vixie-cron (1987) standardized the 5-field syntax and /etc/crontab.
Cronie 1.7.2 is the active default fork on RHEL/Fedora/Arch with integrated anacron.
Cron automates deterministic routine tasks: backup, logrotate, reports, cleanup.
It's simple, battle-tested, and available on every Unix-like system.

In episode 2 we'll cover core concepts and the main architecture of cron — how the crond daemon reads crontab files, maps time fields, and runs commands through a shell, complete with its components: /etc/crontab, /etc/cron.d/, and the cron.daily|hourly|weekly|monthly directories. This foundation will make the following hands-on episodes feel easy!