3 ms·
Huh, it's quite surprising to see the concurrent runs at 02:00 for multiple instances. I guess this can cause quite a bit of weirdness if you use a spec like "
by 0x0 5y ago
Huh, it's quite surprising to see the concurrent runs at 02:00 for multiple instances.
I guess this can cause quite a bit of weirdness if you use a spec like "5,17,32,47 * * * *" (to avoid the "thundering herd" of cronjobs at xx:00) and then getting four concurrent instances running at 02:00 in the daylight switchover hour?
- cuu508 5y agoThe hour specifier in "5,17,32,47 * * * *" is "*", so this would count as a wildcard job, and Debian cron would not run it at xx:00. But, if the hour specifier started with anything but "*", that would be problematic. For example "5,17,32,47 0-23 * * *" appears equivalent, but Debian cron would run this one four times at xx:00 after a time jump. Edit: I just ran the second example – https://gist.github.com/cuu508/7e42e5eecd42babf43f8d0dd0d9873a5 https://gist.github.com/cuu508/7e42e5eecd42babf43f8d0dd0d987...
- 0x0 5y agoInteresting, thanks for running it. And yes I guess I got confused with the hour wildcard. So I guess the takeaway is to avoid non-wildcarded hours such as 0-23 or 0,1,2,3,4,5,6,7