Why Is It Called 'cron'? — The Origin of the Term

The ancient Greeks had two words for time. Kairos meant the opportune moment — the right time for action. Chronos meant sequential, measured time — the tick of the clock, the march of minutes. When Ken Thompson and Brian Kernighan needed a name for Unix’s time-based job scheduler, they reached for chronos. They trimmed it to four letters, and cron was born.

The Story

Cron first appeared in Unix Version 7, released by Bell Labs in 1979. Brian Kernighan — one of the creators of Unix itself — wrote the original implementation. The name itself is transparent: a shortened form of “chronograph” and ultimately the Greek chronos (χρόνος), meaning “time.”

Before cron, Unix had at, a one-shot job scheduler that ran a command at a specified time. But system administrators needed something recurring — daily cleanup, hourly logs, weekly backups. The solution was a daemon that would wake up every minute, check its configuration files, and execute whatever tasks were scheduled for that exact minute.

The configuration file was called crontab — a table of cron jobs. Its format became legendary for both its elegance and its terseness: five time fields followed by a command.

* * * * * command
| | | | |
| | | | +---- Day of week (0-7, Sunday=0)
| | | +------ Month (1-12)
| | +-------- Day of month (1-31)
| +---------- Hour (0-23)
+------------ Minute (0-59)

How It Evolved

The original cron was simple: it read /etc/crontab on startup and every time it checked for work. But as Unix systems grew more complex, so did cron.

Vixie cron (Paul Vixie, 1987): Added per-user crontabs (users could create their own cron jobs) and improved the parsing and reliability. Vixie cron became the standard on BSD and later Linux.

ISC cron: The Internet Systems Consortium maintained and extended Vixie cron through the 1990s. It added environment variable support and better mail handling for job output.

Anacron (1995): For systems that aren’t running 24/7. If a cron job was scheduled for 3 AM but the laptop was asleep, anacron runs it at the next opportunity. The “an” prefix means “not” — “not-chronos,” or time-independent scheduling.

Systemd timers (2010s): Modern Linux systems increasingly use systemd timers as an alternative to cron. They offer calendar events, monotonic timers, and deep integration with systemd’s service management. But cron remains universal, installed on virtually every Unix-like system, often as a fallback.

The crontab format itself became a standard: even Windows Task Scheduler and Kubernetes CronJobs conceptually follow the same five-field schedule syntax.

Did You Know?

The Greek root chronos appears throughout computing. “Synchronous” communication happens at the same time. “Anachronism” is something out of its proper time. “Chronicle” is a record of events in time. Cron, chronometer, chronic, chronological — all from the same root.

The original Bell Labs cron had a security feature: it would mail the output of each cron job to the crontab owner. If a job produced no output, no email was sent. This “mail on error” convention is still the default behavior of most cron implementations.

Every minute — every single minute — cron wakes up and checks whether it has work to do. On a typical Linux server, cron runs about 525,600 checks per year, and the vast majority find nothing to do. That’s the moment-by-moment hum of Unix timekeeping.

FAQ

Related Etymologies