@ttamttam I love your optimism if you actually trust a random linux box (with systemd or without) to run this timer in 5 years, through (supposedly) 1-2 OS upgrades. @rixx
@wink@rixx
Honestly since I switched to NixOS (btw)... Yeah.
But same could be said for Ansible or Chef or any kind of declarative infrastructure as code setup. Systemd timers have been rock solid for me. So, like you implied, the issue is not the timer but making sure the config survives. Good configuration hygiene goes a long way in mitigating this.
@ttamttam@wink likewise, most of my servers have been around for easily five years or more, and while I am far from a professional sysadmin, and I have broken many things, misplacing my systemd files has never been one of them.
@wink@ttamttam@rixx
Realistically, you'd be scheduling things like "1st and 15th of each month" or "first Saturday of each month", maybe annually at most; it just winds up that by the time you implement the useful patterns, you also get impractical ones, like "each time Christmas falls on Tuesday"
Gregory's Server
@wink @rixx
Honestly since I switched to NixOS (btw)... Yeah.
But same could be said for Ansible or Chef or any kind of declarative infrastructure as code setup. Systemd timers have been rock solid for me. So, like you implied, the issue is not the timer but making sure the config survives. Good configuration hygiene goes a long way in mitigating this.