CRON expression for firing a scheduled job between two hours including last one

cron

I have a job scheduled via Quartz and a CRON Expression. The goal of my CRON expression is to run every 10 minutes every day between Monday and Friday between 08:00 AM and 20:00 PM and looks like this:

0 0/10 8-19 ? * MON-FRI

My execution log looks like this:

2010-02-24 19:10:00,140 INFO  - Start
2010-02-24 19:20:00,015 INFO  - Start
2010-02-24 19:30:00,015 INFO  - Start
2010-02-24 19:40:00,015 INFO  - Start
2010-02-24 19:50:00,000 INFO  - Start //Execution expected at 20:00 PM
2010-02-25 08:00:00,000 INFO  - Start
2010-02-25 08:10:00,000 INFO  - Start
2010-02-25 08:20:00,000 INFO  - Start
2010-02-25 08:30:00,000 INFO  - Start
2010-02-25 08:40:00,000 INFO  - Start
2010-02-25 08:50:00,000 INFO  - Start
2010-02-25 09:00:00,000 INFO  - Start
2010-02-25 09:10:00,000 INFO  - Start

I would like that my CRON expression will fire my job at 20:00 PM. Question: Can this be accomplished using one CRON expression? which one?

Best Answer

Why should it run at 20:00? You specify that the hour should be 8-19, so 20:00 doesn't match that. I am not sure if there can be a single line cron expression to accomplish your needs, but you could easily add a line

0 20 * * * ...

in addition to the existing one, that should do the trick.

Related Solutions

Cron – How to Prevent Duplicate Cron Jobs Running

There are a couple of programs that automate this feature, take away the annoyance and potential bugs from doing this yourself, and avoid the stale lock problem by using flock behind the scenes, too (which is a risk if you're just using touch). I've used lockrun and lckdo in the past, but now there's flock(1) (in newish versions of util-linux) which is great. It's really easy to use:

* * * * * /usr/bin/flock -n /tmp/fcj.lockfile /usr/local/bin/frequent_cron_job

Let’s Encrypt – Best Practices for Setting a Cron Job for Certbot Renewal

Monthly is not frequent enough.

This script should run at least weekly, and preferably daily. Remember that certs don't get renewed unless they are near to expiration, and monthly could cause your existing certs to occasionally be expired already before they get renewed.

The name of the program is certbot, which was renamed from letsencrypt. If you are still using letsencrypt, you need to update to the current version.

Aside from those issues, it's about the same as my cron jobs.

43 6 * * * certbot renew --post-hook "systemctl reload nginx"

Note: in 18.04 LTS the letsencrypt package has been (finally) renamed to certbot. It now includes a systemd timer which you can enable to schedule certbot renewals, with systemctl enable certbot.timer and systemctl start certbot.timer. However, Ubuntu did not provide a way to specify hooks. You'll need to set up an override for certbot.service to override ExecStart= with your desired command line, until Canonical fixes this.

Best Answer

Related Solutions

Cron – How to Prevent Duplicate Cron Jobs Running

Let’s Encrypt – Best Practices for Setting a Cron Job for Certbot Renewal

Related Topic