Linux Cron Jobs: Scheduling and Automation

Linux Linux 8 min read 1618 words Beginner ExcellentWiki Editorial Team

Cron jobs are the backbone of Linux automation, running scripts at scheduled times without manual intervention. This guide focuses on practical cron usage for system administration, backups, monitoring, and maintenance tasks.

Understanding Cron

The cron daemon (crond) checks crontab files every minute and executes commands that match the current time. Each user can have their own crontab, and the system has its own for maintenance tasks.

Crontab Fields

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

Special operators:

* — any value (every minute, hour, etc.)
, — list of values (1,15 = at minutes 1 and 15)
- — range (1-5 = Monday through Friday)
/ — step (*/5 = every 5 units)

Simple Schedules

# Run every night at midnight
0 0 * * * /usr/local/bin/daily-backup.sh

# Run every hour
0 * * * * /usr/local/bin/hourly-check.sh

# Run every 10 minutes
*/10 * * * * /usr/local/bin/health-check.sh

# Run twice daily (8 AM and 8 PM)
0 8,20 * * * /usr/local/bin/daily-report.sh

# Run on the 1st and 15th of each month
0 3 1,15 * * /usr/local/bin/billing-cycle.sh

# Run every weekday at 9:30 AM
30 9 * * 1-5 /usr/local/bin/standup-reminder.sh

Managing Crontabs

# Edit crontab (opens default editor)
crontab -e

# View current crontab
crontab -l

# View another user's crontab (root)
sudo crontab -u www-data -l

# Remove crontab
crontab -r

# Install crontab from file
crontab /path/to/my-cron.txt

# Edit with specific editor
EDITOR=nano crontab -e

Environment and Path

Cron runs with a sparse environment. Always set variables at the top of your crontab:

# Environment variables in crontab
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
MAILTO=admin@example.com
HOME=/home/username

# Use absolute paths or set PATH
0 3 * * * /home/username/scripts/backup.sh

# Redirect output to prevent mail
0 3 * * * /home/username/scripts/backup.sh >> /var/log/backup.log 2>&1

Practical Automation Examples

Database Backup with Rotation

# /etc/cron.d/db-backup
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

# Daily PostgreSQL backup at 1 AM, keep 30 days
0 1 * * * postgres \
    /usr/local/bin/pg-backup.sh \
    >> /var/log/pg-backup.log 2>&1

Log Rotation Script

# /usr/local/bin/rotate-logs.sh
#!/bin/bash
LOGDIR="/var/log/myapp"
RETENTION_DAYS=90

# Compress logs older than 1 day
find "$LOGDIR" -name "*.log" -mtime +1 -exec gzip {} \;

# Delete logs older than retention period
find "$LOGDIR" -name "*.gz" -mtime +"$RETENTION_DAYS" -delete

SSL Certificate Expiry Monitoring

# /etc/cron.d/ssl-check
0 9 * * 1 root /usr/local/bin/check-ssl.sh example.com

#!/bin/bash
DOMAIN="$1"
EXPIRY=$(echo | openssl s_client -servername "$DOMAIN" -connect "$DOMAIN":443 2>/dev/null | openssl x509 -noout -enddate | cut -d= -f2)
EXPIRY_EPOCH=$(date -d "$EXPIRY" +%s)
NOW_EPOCH=$(date +%s)
DAYS_LEFT=$(( (EXPIRY_EPOCH - NOW_EPOCH) / 86400 ))

if [[ $DAYS_LEFT -lt 30 ]]; then
    echo "SSL certificate for $DOMAIN expires in $DAYS_LEFT days"
fi

Disk Usage Monitoring

# /etc/cron.d/disk-check
0 */4 * * * root /usr/local/bin/check-disk.sh

#!/bin/bash
THRESHOLD=90

df -h | grep -vE '^Filesystem|tmpfs|cdrom' | while read -r line; do
    usage=$(echo "$line" | awk '{print $5}' | sed 's/%//')
    mount=$(echo "$line" | awk '{print $6}')
    if [[ $usage -ge $THRESHOLD ]]; then
        echo "WARNING: Disk usage on $mount is at ${usage}%"
    fi
done

Troubleshooting Cron

Common Problems

Cron daemon not running

systemctl status cron
sudo systemctl enable cron && sudo systemctl start cron

Script works manually but not in cron
- Cron uses a minimal PATH (usually /usr/bin:/bin)
- Use absolute paths for all commands
- Set PATH and SHELL at the top of the crontab
- Test with: env -i HOME=$HOME PATH=/usr/bin:/bin SHELL=/bin/bash bash -l /path/to/script
No output or logs
- Redirect stdout/stderr: command >> /var/log/output.log 2>&1
- Check mail with the mail command
- Check syslog: grep CRON /var/log/syslog

Syntax errors

# Validate crontab by reinstalling it
crontab -l | crontab -

Permissions issues

# Script must be executable
chmod +x /path/to/script.sh

# Script owner must match crontab owner
ls -la /path/to/script.sh

Debugging Tools

# Watch cron in real time
journalctl -f -u cron

# Check if specific command ran
grep "mycommand" /var/log/syslog

# Run with debug logging
* * * * * /bin/bash -x /path/to/script.sh >> /tmp/debug.log 2>&1

Cron Security

# Restrict cron usage with allow/deny files
/etc/cron.allow    # only listed users can use cron
/etc/cron.deny     # listed users cannot use cron

Real-World Implementation Tips

Production Considerations

When moving from development to production, several factors become critical. Error handling should be comprehensive — every external call (database, API, file system) should have proper error checking, logging, and retry logic where appropriate. Performance monitoring through metrics and structured logging helps identify bottlenecks before they affect users.

Testing Strategy

A thorough testing approach combines multiple levels:

Unit tests verify individual functions and methods in isolation
Integration tests validate that components work together correctly
Edge case tests cover boundary conditions, empty inputs, and error states
Performance tests ensure the system meets latency and throughput requirements

Test data should be realistic but controlled. Mock external dependencies to make tests fast and deterministic. Aim for tests that are independent, repeatable, and fast enough to run on every commit.

Documentation

Good documentation is essential for maintainable code. Follow these principles:

Document the “why” not just the “what” — explain design decisions
Keep examples up to date with the code
Include usage examples for public APIs
Document configuration options and their defaults
Explain error conditions and recovery strategies

Security Best Practices

Security should be considered throughout development:

Validate all inputs at system boundaries
Use parameterized queries for database access
Store secrets in environment variables or secret managers
Keep dependencies updated to patch vulnerabilities
Apply the principle of least privilege

Performance Optimization

Optimize based on measured data, not assumptions:

Profile before optimizing — identify actual bottlenecks
Measure the impact of each change
Consider the trade-off between speed and readability
Cache expensive operations with appropriate invalidation
Use connection pooling for database and network resources

Monitoring and Observability

Production systems need visibility:

Structured logging with correlation IDs for request tracking
Metrics for latency, throughput, error rates, and resource usage
Health check endpoints for load balancers and orchestration
Distributed tracing for request flows across services
Alerts for anomaly detection based on baselines

These patterns apply across all programming languages and frameworks. The specific implementation varies, but the principles remain consistent.

FAQ

Q: Can I run cron jobs every 30 seconds? A: Cron’s minimum is 1 minute. Use a loop inside the job: * * * * * for i in $(seq 0 30 59); do (sleep $i; command) & done

Q: How do I prevent overlapping cron jobs? A: Use flock (file lock): * * * * * /usr/bin/flock -n /tmp/mylock.lock /path/to/command

Q: What happens if the system is off when a job should run? A: The job is skipped. Cron does not catch up after downtime. For missed jobs, use anacron for daily/weekly/monthly tasks.

Q: How do I run a job on every reboot? A: Use @reboot in the crontab or place a script in /etc/rc.local.

Q: Where are cron logs stored? A: Debian/Ubuntu: /var/log/syslog. RHEL/CentOS: /var/log/cron. Modern systems: journalctl -u cron.

Q: Can I use environment variables in cron? A: Yes, define them at the top of the crontab. Each variable applies to all subsequent entries.

Cron Job Best Practices

Logging and Output

Always redirect cron output to avoid filling the system mailbox:

# Log stdout and stderr to separate files
30 2 * * * /home/user/backup.sh >> /var/log/backup.log 2>&1

# Suppress all output (use with caution)
0 3 * * * /home/user/cleanup.sh > /dev/null 2>&1

Environment Variables

Cron runs with minimal environment. Always use full paths and set variables:

# Set environment in crontab
PATH=/usr/local/bin:/usr/bin:/bin
SHELL=/bin/bash
HOME=/home/user
MAILTO=admin@example.com

0 4 * * * $HOME/scripts/daily-report.sh

Randomizing Job Times

Avoid having all cron jobs run at the same minute:

# Spread jobs across minutes to avoid load spikes
17 3 * * * job_a.sh
42 3 * * * job_b.sh
# Use random sleep in scripts
0 3 * * * sleep $((RANDOM % 300)) && job.sh

Monitoring Cron Jobs

# Check cron service status
systemctl status cron
# View cron logs
grep CRON /var/log/syslog
# List all users' crontabs
for user in $(cut -f1 -d: /etc/passwd); do echo "=== $user ==="; crontab -u $user -l 2>/dev/null; done

For a comprehensive overview, read our article on Bash Scripting Basics.

For a comprehensive overview, read our article on Cron Jobs Guide.