Linux Crontab Guide — Setup, Examples & Troubleshooting (2026)

Linux crontab is the built-in job scheduler on every Linux distribution and macOS. Run crontab -e to open your schedule, add a cron expression followed by a command, save, and the system handles the rest. Here is the complete setup, real examples, and fixes for every common problem.

Crontab Commands

Command	What It Does
crontab -e	Edit your personal crontab (opens in default editor)
crontab -l	List all your current cron jobs
crontab -r	Remove your entire crontab (use carefully — deletes ALL jobs)
crontab -r -i	Remove with confirmation prompt (safer)
sudo crontab -e	Edit the root user crontab
sudo crontab -l -u www-data	List cron jobs for a specific user (requires root)

Your First Cron Job

1. Open your terminal
2. Run crontab -e — choose nano if prompted for an editor (easiest for beginners)
3. Add this line at the bottom: */5 * * * * echo "cron works" >> /tmp/crontest.log 2>&1
4. Save and exit (in nano: Ctrl+O, Enter, Ctrl+X)
5. Wait 5 minutes, then check: cat /tmp/crontest.log
6. If you see "cron works" — your crontab is functioning
7. Remove the test job: run crontab -e and delete the line

Real-World Crontab Examples

Cron Expression	Command	Purpose
0 2 * * *	/home/user/scripts/backup.sh >> /var/log/backup.log 2>&1	Nightly backup at 2 AM
*/5 * * * *	/usr/bin/python3 /home/user/healthcheck.py	Health check every 5 min
0 9 * * 1-5	/home/user/scripts/report.sh | mail -s "Daily Report" [email protected]	Weekday 9 AM report
0 0 * * 0	/usr/sbin/logrotate /etc/logrotate.conf	Weekly log rotation
0 */6 * * *	/usr/bin/certbot renew --quiet	SSL cert renewal check every 6 hrs
30 4 1 * *	/home/user/scripts/monthly-cleanup.sh > /dev/null 2>&1	Monthly cleanup, no output

Crontab vs System Cron Directories

Linux has two ways to schedule cron jobs: user crontabs and system cron directories. Both are active simultaneously.

Location	Managed By	Use Case	Includes Username Field
crontab -e	Individual users	User-specific scheduled tasks	No (runs as that user)
/etc/crontab	System admin	System-wide jobs with user specification	Yes (root, www-data, etc.)
/etc/cron.d/	Package managers, admin	Individual cron files per service	Yes
/etc/cron.hourly/	System (run-parts)	Scripts that run every hour	N/A (just executable scripts)
/etc/cron.daily/	System (run-parts)	Scripts that run daily (~6:25 AM)	N/A
/etc/cron.weekly/	System (run-parts)	Scripts that run weekly (Sunday ~6:47 AM)	N/A
/etc/cron.monthly/	System (run-parts)	Scripts that run monthly (1st ~6:52 AM)	N/A

The /etc/cron.daily/ and similar directories are the simplest option for interval-based jobs — just drop an executable script into the directory. No cron expression needed. The system scheduler (anacron) handles the timing.

The #1 Problem: PATH Issues

Cron runs with a minimal environment — typically PATH=/usr/bin:/bin. This means commands that work in your terminal may fail in cron because cron cannot find them.

Fix: always use full paths in cron jobs.

• Instead of python3 script.py, use /usr/bin/python3 /full/path/to/script.py
• Instead of node app.js, use /usr/local/bin/node /full/path/to/app.js
• Find any command path with: which python3 or which node

Alternatively, set PATH at the top of your crontab:

• Add PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin as the first line in crontab -e
• This applies to all jobs below it in that crontab

Troubleshooting Cron Jobs

Problem	Diagnosis	Fix
Job not running at all	Check if cron service is active: systemctl status cron	sudo systemctl start cron && sudo systemctl enable cron
Command not found errors	PATH issue — cron has minimal PATH	Use full paths: /usr/bin/python3 instead of python3
Permission denied	Script not executable	chmod +x /path/to/script.sh
No output or error messages	Output goes to mail or nowhere	Add >> /tmp/job.log 2>&1 to capture output
Job runs but produces wrong results	Environment variables missing	Source your env in the script: source /home/user/.env
Job runs at wrong time	Timezone mismatch	Check with timedatectl — cron uses system timezone
Job seems to run multiple times	Overlapping executions	Add flock lock: flock -n /tmp/job.lock /path/to/script.sh
Cron email flooding inbox	Every job output goes to user mail	Add > /dev/null 2>&1 or set MAILTO="" in crontab

Checking Cron Logs

• Ubuntu / Debian: grep CRON /var/log/syslog
• CentOS / RHEL / Fedora: cat /var/log/cron
• Real-time monitoring: tail -f /var/log/syslog | grep CRON
• Systemd journal: journalctl -u cron --since "1 hour ago"

Cron logs show when each job started but NOT the output. To capture job output, redirect it in the cron line itself: 0 9 * * * /path/to/job.sh >> /var/log/myjob.log 2>&1

macOS Crontab vs launchd

macOS supports crontab identically to Linux. However, Apple officially recommends launchd as the preferred scheduler:

Feature	crontab	launchd (plist)
Setup complexity	✓ Simple — one-line cron expression	~Complex — XML plist files
Time-based scheduling	✓ Yes — standard cron syntax	✓ Yes — StartCalendarInterval
Run after sleep/wake	✗ Missed jobs are skipped	✓ Catches up missed jobs
Event-based triggers	✗ Time only	✓ File changes, network events, login
Logging	~Manual redirect	✓ Built-in stdout/stderr paths
Process management	✗ No restart on failure	✓ KeepAlive, restart policies
Best for	✓ Simple scheduled scripts	~Complex daemons and agents

For simple scheduled tasks (backups, scripts, health checks), crontab on macOS is perfectly fine. Use launchd when you need event-driven triggers or want the system to catch up on missed jobs after sleep.

When Cron Is Not Enough

Cron is excellent for simple, time-based scheduling on a single machine. You will outgrow it when you need:

• Distributed scheduling — multiple servers need coordinated job execution. Look at Kubernetes CronJobs, Nomad, or cloud schedulers.
• Workflow orchestration — jobs with dependencies (run B only after A succeeds). Use Airflow, Temporal, Prefect, or Dagster.
• Retry and failure handling — automatic retries with backoff. Use task queues like Celery, Bull, or Sidekiq.
• Sub-minute intervals — cron's minimum is once per minute. For faster, use systemd timers (with OnUnitActiveSec) or event-driven architecture.
• Audit trail — who changed what schedule and when. Use version-controlled CI/CD cron configs instead of editing crontab directly.

Developer Tools

• Cron Expression Generator — build and validate cron expressions visually
• Code Explainer — paste a shell script and understand what it does before scheduling it
• Timestamp Converter — convert between timezones for servers in different regions
• JSON Formatter — format config files for cloud scheduler setups
• Diff Checker — compare crontab exports before and after changes
• Regex Tester — build grep patterns for parsing cron logs
• SQL Formatter — format database queries executed by your cron scripts
• Code Formatter — clean up bash scripts before adding them to cron