0
1

[–] ThisIsMyRealName 0 points 1 point (+1|-0) ago 

I've written services and timers.

DynamicUsers? StateDir? Used .path, .network,

No, I haven't messed with those yet.

0
0

[–] TeranNotTerran [S] ago 

The basic stuff works well but there's lots of bugs. Like going from User= to DynamicUser= on a service could break it if it had the same name. systemd-resolved would stop serving requests for no reason. systemd-timesyncd failed for me once with no errors, leaving me with a bad clock.

I do like timers a lot vs cron. And being able to do stuff like systemctl list-units --state=failed is nice for monitoring.

0
0

[–] ThisIsMyRealName ago 

systemd is a large and young enough codebase that it should be expected there are bugs. We're probably another decade off before all of the show-stopping bugs are found and patched.

going from User= to DynamicUser= on a service could break it if it had the same name

Why would you do that though? lol

systemd-timesyncd failed for me once with no errors, leaving me with a bad clock

And that shouldn't happen. There's no excuse for it. Fucking up time isn't something you, well, typically fuck with. I haven't experienced that bug though.