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 |
filbranden
left a comment
There was a problem hiding this comment.
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.