Crontab Generator

Q: How to set cron for every 5 minutes?

Use */5 * * * * — the */5 in the minute field means 'every 5th minute'. The asterisks in the remaining fields mean 'any value', so the job runs at minutes 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55 of every hour, every day.

Q: How to goaccess generate html report every hour crontab example?

Add this line to your crontab (crontab -e): 0 * * * * /usr/bin/goaccess /var/log/nginx/access.log -o /var/www/html/report.html --log-format=COMBINED. This runs GoAccess at minute 0 of every hour, reads your Nginx access log, and writes an HTML report. Adjust the log path, output path, and --log-format to match your setup.

About Cron Jobs and Crontab

Cron is a time-based job scheduler in Unix-like operating systems. Our crontab generator helps you create, validate, and understand cron expressions for automating tasks and scheduling jobs.

Generate cron expressions with visual interface
Validate and explain existing cron expressions
Common presets for frequent scheduling patterns
Support for advanced cron syntax and special characters
Real-world examples and best practices

Cron Expression Format

* * * * * command

│ │ │ │ │
│ │ │ │ └─── Day of Week (0-7, Sunday=0 or 7)
│ │ │ └───── Month (1-12)
│ │ └─────── Day of Month (1-31)
│ └───────── Hour (0-23)
└─────────── Minute (0-59)

Special Characters

*Any value

,Value list

-Range of values

/Step values

Special Strings

@yearly or @annually

@monthly

@weekly

@daily or @midnight

@hourly

Frequently Asked Questions

How to generate a crontab?

Use the utilAZ Crontab Generator: select the minute, hour, day-of-month, month, and day-of-week fields using the visual interface or type the expression directly. The tool validates your input in real time, shows the next scheduled execution times, and provides a human-readable explanation. Copy the resulting expression into your crontab file (crontab -e) or CI/CD pipeline.

What is the cron expression 30 4 1 15 * 5?

In a standard 5-field cron format this would be interpreted as: minute 30, hour 4, day-of-month 1 and 15, any month, day-of-week 5 (Friday). So it fires at 04:30 on the 1st and 15th of every month AND every Friday. Note: when both day-of-month and day-of-week are set, most cron implementations run the job when either condition is met (OR logic).

What is a 7 character cron expression?

A 7-field cron expression adds a seconds field at the beginning and a year field at the end: seconds minute hour day-of-month month day-of-week year. This extended format is used by frameworks like Quartz Scheduler (Java), Spring, and Salesforce. Standard Unix/Linux crontab uses only 5 fields (minute through day-of-week).

How to set cron for every 5 minutes?

Use */5 * * * * — the */5 in the minute field means "every 5th minute". The asterisks in the remaining fields mean "any value", so the job runs at minutes 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55 of every hour, every day.

How to goaccess generate html report every hour crontab example?

Add this line to your crontab (crontab -e): 0 * * * * /usr/bin/goaccess /var/log/nginx/access.log -o /var/www/html/report.html --log-format=COMBINED. This runs GoAccess at minute 0 of every hour, reads your Nginx access log, and writes an HTML report. Adjust the log path, output path, and --log-format to match your setup.

Common Cron Expression Examples

0 0 * * * Daily at midnight

Runs every day at 12:00 AM

*/15 * * * * Every 15 minutes

Runs every 15 minutes throughout the day

0 9 * * 1-5 Weekdays at 9 AM

Runs at 9:00 AM, Monday through Friday

0 0 1 * * First day of every month

Runs at midnight on the 1st of each month

0 2 * * 0 Sunday at 2 AM

Runs at 2:00 AM every Sunday

Managing Crontab

Basic Commands:

# Edit current user's crontab
crontab -e

# List current user's cron jobs
crontab -l

# Remove all cron jobs for current user
crontab -r

# Edit another user's crontab (as root)
crontab -u username -e

# List system-wide cron jobs
cat /etc/crontab

Example Crontab Entry:

# Backup database daily at 2 AM
0 2 * * * /usr/local/bin/backup-db.sh

# Clean temp files every hour
0 * * * * /bin/rm -rf /tmp/temp_*

# Send weekly report on Fridays at 5 PM
0 17 * * 5 /home/user/send_report.py

# Restart service every 6 hours
0 */6 * * * /usr/bin/systemctl restart myservice

Cron Best Practices

Use absolute paths: Always specify full paths to commands and files
Set environment variables: Define PATH, SHELL, and other variables in crontab
Redirect output: Use >> /var/log/cronlog 2>&1 to capture output and errors
Test your commands: Run commands manually before adding to cron
Use locking: Prevent overlapping executions with flock or similar
Monitor execution: Check logs regularly and set up alerting
Document your jobs: Add comments explaining what each job does

Common Use Cases

Database backups and maintenance
Log file rotation and cleanup
System monitoring and alerts
File synchronization and transfers
Web scraping and data collection
Report generation and distribution
Cache clearing and optimization
Security scans and updates