Technical Guide: Crontab Architecture, Syntax Standards, and Execution Patterns
Cron is the standard time-based job scheduler across UNIX-like operating systems. Originally developed by Brian Kernighan and released with Version 7 Unix in 1979, the cron daemon reads crontab configuration tables and runs scheduled shell commands in background processes. Understanding the subtle syntax differences between standard Vixie cron, Quartz, and cloud event rules prevents common production scheduling failures.
Comparison of Cron Flavors and Schedulers
| Scheduler | Field Count | Order of Fields | Sunday Value | Day-of-Month & Day-of-Week Logic |
|---|---|---|---|---|
| POSIX / Vixie Cron (Linux) | 5 | min hr dom mon dow | 0 or 7 | Logical OR (union if both specified) |
| Extended Linux / BSD | 6 | sec min hr dom mon dow | 0 or 7 | Logical OR (union if both specified) |
| Quartz / Spring Boot | 6 (or 7) | sec min hr dom mon dow (year) | 1 (1=SUN, 7=SAT) | Requires question mark (?) in one field |
| AWS EventBridge / CloudWatch | 6 | min hr dom mon dow year | 1 (1=SUN, 7=SAT) | Requires question mark (?) in one field |
Six Common Reasons Production Cron Jobs Fail
Many developers configure a cron expression that appears correct in testing but fails when deployed to a server. These issues usually stem from runtime environment constraints rather than syntax errors:
- Restricted Environment Variables: The cron daemon executes tasks with a minimal environment. Variables like
PATH,HOME, and user shell settings are not inherited from your interactive terminal session. Always specify the full binary path (for example,/usr/bin/nodeinstead ofnode) or declarePATH=/usr/local/bin:/usr/bin:/binat the top of your crontab file. - Unescaped Percent Signs: In standard crontab entries, the percent sign (
%) functions as a newline character unless escaped with a backslash. Runningmysqldump prod > backup-$(date +%F).sqlwill fail. Escape the symbol as\%F. - Timezone Assumptions: The cron daemon runs on the system clock timezone. If your server runs in UTC and you schedule a task for 02:00 expecting local time, the job runs at an unexpected hour. Modern versions of Vixie cron support
CRON_TZ=America/New_Yorkat the top of the file to fix this. - Silent Discarding of Errors: By default, cron attempts to send output through local mail. If no mail transfer agent (MTA) like Postfix is active, errors disappear silently. Explicitly redirect standard error (
2>&1) to a log file. - Working Directory Expectations: Cron tasks launch from the user's home directory, not your application root. Scripts that use relative file paths will fail to locate resources. Change directory before running the command:
cd /var/www/app && ./run.sh. - Overlapping Job Executions: If a job scheduled every minute takes longer than 60 seconds to process, multiple concurrent instances spawn and exhaust memory or database locks. Use tools like
flock -n /var/lock/myjob.lock /app/script.shto prevent overlapping runs.
Cron Operator Reference
Matches every allowed value in the field. In the minute position, this triggers every single minute.
Separates explicit items in a list. For example, 1,15,30 in minutes triggers at minutes 1, 15, and 30.
Defines an inclusive range of values. For example, 1-5 in weekdays runs Monday through Friday.
Specifies step increments. */15 in minutes runs every 15 minutes starting from zero.
Frequently Asked Questions
How do I edit my crontab file in Linux or macOS?
Open a terminal and run 'crontab -e'. This launches your default terminal editor (such as nano or vim) with your personal crontab. Save and exit the editor, and the daemon automatically validates and installs the new schedule.
What does the @reboot macro do?
@reboot is a non-standard extension supported by Vixie Cron and modern systemd wrappers. It runs the associated command once after system initialization before other scheduled jobs start.
Can I run a cron job every 30 seconds?
Standard UNIX crontab has a minimum resolution of 1 minute. To achieve sub-minute scheduling, use a 6-field scheduler like Quartz, a systemd timer, or invoke two tasks in crontab using sleep: '* * * * * /app/job.sh' and '* * * * * sleep 30; /app/job.sh'.
Where does cron store job execution logs?
On Debian/Ubuntu systems, cron events are written to /var/log/syslog or /var/log/cron.log. On RHEL, CentOS, and Fedora, check /var/log/cron. On modern systemd Linux, use 'journalctl -u cron' or 'journalctl -u crond'.