Scheduling with Cron & Crontab Automation
The `cron` daemon is the standard Unix time-based job scheduler. Users configure automated recurring tasks (crontabs) using a 5-field time expression: Minute (0-59), Hour (0-23), Day of Month (1-31), Month (1-12), and Day of Week (0-7).
"Cron is like an automated alarm clock connected to a programmable robot: at the exact minute and hour you set, the alarm goes off and the robot runs your script."
Deep Dive: How It Works
The 5-Field Anatomy: `* * * * * command` (Minute Hour Day-of-Month Month Day-of-Week).
Common Expressions: `*/15 * * * *` (every 15 mins), `0 2 * * *` (daily at 2:00 AM), `0 0 * * 0` (every Sunday midnight), `@reboot` (run once at system startup).
The Cron Environment Trap: Cron runs with a minimal, stripped-down `$PATH` (`/usr/bin:/bin`) and no user profile environment variables.
Syntax Blueprint
# ┌───────────── minute (0 - 59) # │ ┌───────────── hour (0 - 23) # │ │ ┌───────────── day of month (1 - 31) # │ │ │ ┌───────────── month (1 - 12) # │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday=0 or 7) # │ │ │ │ │ # * * * * * command_to_execute
Crontab entries consist of 5 time fields followed by the absolute command path.
Core Rules to Remember
Common Beginner Traps & How to Fix Them
A script runs fine in interactive terminal but fails silently when triggered by cron.Why it happens: Cron lacks your interactive `$PATH`, environment variables, and active working directory.
How to fix: Set explicit `PATH=/usr/local/bin:/usr/bin:/bin` inside crontab and use absolute paths.
Live Interactive Example
Hit Run Code to see it liveYour Turn: Micro Challenge
No pressure! Edit the starter code below and test your solution with instant feedback.
Verify Daily Cron Schedule Expression
- Echo "0 0 * * * /opt/backup.sh" representing daily midnight backup execution.
Finished reading and practicing?
Mark this lesson as completed to update your course progress.