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.
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.
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.
That's part of my point. Because it's so big, there's going to be lots of bugs. Because of it's position in the stack, they are pretty major bugs. But in general, it's un-UNIX like.
going from User= to DynamicUser= on a service could break it if it had the same name
Why would you do that though? lol
Because of iterative development. Started with User=, learned about DynamicUser=, so went to enable it and things broke. I have even had issues with DynamicUser=yes and Group=anything, I had to give it GIDs.
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.
I agree, hopefully rare. But name resolution is almost as important that that breaks all the time. There's so many good existing utilities, I don't know why systemd has to replace them all.
view the rest of the comments →
[–] 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.
Why would you do that though? lol
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.
[–] TeranNotTerran [S] ago
That's part of my point. Because it's so big, there's going to be lots of bugs. Because of it's position in the stack, they are pretty major bugs. But in general, it's un-UNIX like.
Because of iterative development. Started with User=, learned about DynamicUser=, so went to enable it and things broke. I have even had issues with DynamicUser=yes and Group=anything, I had to give it GIDs.
I agree, hopefully rare. But name resolution is almost as important that that breaks all the time. There's so many good existing utilities, I don't know why systemd has to replace them all.