New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sysusers,tmpfiles: re-create systemd-network, systemd-resolve and systemd-timesync #9586
Conversation
…temd-timesync This partially reverts d4e9e57, 0187368, and 4240cb0. The services systemd-networkd, systemd-resolved, and systemd-timesyncd enable DynamicUsers= and have bus interfaces. Unfortunately, these has many problems now. Let us create the relevant users, at least, tentatively. Fixes systemd#9503.
Looks good to me. I'd take it even further and drop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
The change to systemd.conf.m4
is the exact workaround I'm using on my host right now.
Thanks for the clarification that it's due to DynamicUser=no that I'm seeing this behavior... But that's for my workaround to #9583 so I'll try to attack that next. (I'll make sure when I do I preserve the behavior of chown()ing RuntimeDirectory= even if the user already exists.)
Cheers!
Filipe
After merging this PR, the function has almost the same functionality as |
Just for reference, I think I'm experiencing the same problem, currently.
|
This partially reverts d4e9e57, 0187368, and 4240cb0.
The services systemd-networkd, systemd-resolved, and systemd-timesyncd enable DynamicUsers= and have bus interfaces. Unfortunately, these has many problems now. Let us create the relevant users, at least, tentatively.
Fixes #9503.