Cron job every weekday at 9am

To run a cron job every weekday at 9am, use 0 9 * * 1-5. At 09:00 on weekdays.

  • Free
  • No Sign-Up
  • Runs in Your Browser

Runs

Next Runs

Your time zone
Monday12 Oct 2026, 09:00
Tuesday13 Oct 2026, 09:00
Wednesday14 Oct 2026, 09:00
Thursday15 Oct 2026, 09:00
Friday16 Oct 2026, 09:00

Crontab Line

0 9 * * 1-5 /path/to/job.sh >> /var/log/cron-job.log 2>&1

Cron Expression Generator

0 9 * * 1-5 explained

Expression0 9 * * 1-5
MeaningAt 09:00 on weekdays
Runs per Week5
Crontab Line0 9 * * 1-5 /path/to/job.sh
systemd OnCalendarMon..Fri *-*-* 09:00:00
Time ZoneThe server's, unless CRON_TZ is set

Cron checks the schedule once a minute and starts the job at the start of each matching minute, in the server's time zone.

If a run can take longer than the gap between runs, stop runs overlapping with flock: 0 9 * * 1-5 flock -n /tmp/job.lock /path/to/job.sh. A second copy then exits straight away instead of piling up.

Cron runs jobs with a minimal environment: use full paths, and send output to a log file (>> /var/log/job.log 2>&1) so errors are not lost.

Questions

How do I run a cron job every weekday at 9am?
Run crontab -e and add: 0 9 * * 1-5 /path/to/job.sh
How do I check the cron job ran?
Look in the job's own log if it writes one, or the system log: grep CRON /var/log/syslog on Debian and Ubuntu, or journalctl -u cron (cron.service is crond on RHEL).
What is the systemd timer equivalent of 0 9 * * 1-5?
OnCalendar=Mon..Fri *-*-* 09:00:00 in a .timer unit. systemd timers can also catch up on missed runs with Persistent=true.

Run servers for other people?

Frabs stops the abuse their VMs send out, and keeps your network off blocklists.