>On Thu, 25 Feb 2021 00:28:55 -0500, MegaWattz wrote:
>>
>> Doesn't happen on Debian-derived systems.
>>
>> BUT, if I reboot a TumbleWeed box it runs ALL the Systemd
>> timer services. The particular interest is time-layered backups.
>> They're supposed to run a week to a month apart. Works
>> perfectly, UNLESS you reboot.
>>
>> I've tried all the obvious params in the timers, no good
>> effect. They all have the usual lines for when they
>> should run.
>>
>> Any ideas ? Clues ? Rumors ? Incantations ? Sacrifices
>> to Computus ?
>
>Can't you look instead into cron or anacron?
>
><
https://www.tecmint.com/cron-vs-anacron-schedule-jobs-using-anacron-on-linux/>
WAS using cron. But again TW (and many OSuse) had a
weirdness - root cron-jobs often didn't run UNLESS you
opened-up the crontab in nano or something and then
saved it again. You didn't have to really change anything
at all, just add and remove a space so it thought it was
saving something new. THEN the cronjobs would work
properly until the next rebooot. This is why I went to timers.
There was some old - five years ? - postings about similar
cron issues on OSuse. CLAIMED it was fixed. Maybe
somebody copied-over some old code ?
>Using anacron here and all works like designed.
>
>Must admin that I never dealt with SystemD timers though and might get
>it all wrong.
They are pretty straightforward actually. You need the timer service
and a service the timer starts up. Only the timer is "active", the
target just sits there being stupid until called. You can set days,
hours, weeks, months, date-ranges and conditions - cron on
steroids.
Anyway, as I said, they work as advertised on Deb systems, so
this is a OSuse thing. I'd RATHER use cron, it's by far the
most well-established solution. Systemd is building a city so
you can have a lightswitch .....