Crontab generator

Writing a crontab line by hand means remembering field order and syntax, and a mistake can mean a backup that never runs or a job that fires every minute. This generator lets you choose the schedule with options, then produces the matching cron expression and a plain-English description to confirm it.

How to use it

1. Choose when the job should run: every N minutes, specific hours, certain weekdays or days of the month.
2. Read the generated expression and its description.
3. Add your command and paste the line into crontab -e.

A complete crontab line

30 3 * * 0 /usr/local/bin/backup.sh >> /var/log/backup.log 2>&1

This runs the backup script every Sunday at 03:30 and appends both output and errors to a log file.

Best practices

• Use absolute paths. Cron runs with a minimal PATH, so commands that work in your shell may not be found.
• Redirect output. Otherwise cron tries to email it, and errors disappear silently on systems without mail.
• Set environment variables such as SHELL, PATH or MAILTO at the top of the crontab.
• Escape percent signs. In crontab, an unescaped % becomes a newline, so date +%F must be written as date +\%F.
• Avoid overlaps. Wrap long jobs with flock so a slow run does not start a second copy.
• Spread load. Avoid scheduling everything at minute 0; pick odd minutes like 7 or 23.

Useful commands

• crontab -l lists your jobs.
• crontab -e edits them.
• grep CRON /var/log/syslog shows whether jobs ran on Debian and Ubuntu.