Imagine wondering “When’s the next time that Christmas will be a Tuesday/Wednesday, for those sweet optimal public holidays (Jan 1st being exactly a week later)?”
Now imagine asking, idk, google or Siri or god forbid an actual calendar, instead of turning to the best tool for the job: systemd.
@lambisio Yeah, well, I’m feeling conflicted bth. On the one hand, yes, systemd is eating everything.
On the other hand, this is for systemd-timers, and they are just so *nice*.
@lambisio @xahteiwi Not sure – I thought "* * 13 * 5" meant "both on Fridays and on the 13th of each month", and https://crontab.guru/#0_0_13_*_5 agrees.
In any case a huge advantage of systemd timers is your ability to query them for next / scheduled / past runs like this fwiw.
@rixx @xahteiwi That's weird. I mean, 30 6 * * * means "at 6:30" and not "every half hour and also at 6:00". So it'd be extra weird if dow/dom were specialcased that way.
But even then, that doesn't justify "solving" the problem by subsuming it into systemd. Pretty sure there's like at leats other 200 tools to do the job.
(No, NTP is *not* one of them!)
rixx
Lucho, dando piña a la pizza
Florian Haas
Comrade elronxenu