You can login if you already have an account or register by clicking the button below.
Registering is free and all you need is a username and password. We never ask you for your e-mail.
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.
view the rest of the comments →
[–] TeranNotTerran [S] 0 points 1 point 1 point (+1|-0) ago
Have you written services? DynamicUsers? StateDir? Used .path, .network, or .timer?
[–] ThisIsMyRealName 0 points 1 point 1 point (+1|-0) ago
I've written services and timers.
No, I haven't messed with those yet.
[–] 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=failedis nice for monitoring.