3708c0f455931c8cb5fed149923e5a995c2e3fbf
This partially reverts25de7aa7b9. I don't think the change was intended there. The problem I'm trying to solve: for /dev/kvm we get first an ADD uevent, and then CHANGE whenever something connects or disconnects to the character device. The rules in 50-default-udev.rules set UID, GID, and MODE on ADD, but not on CHANGE. When the change event happens, we would reset the ownership and permissions. This happens because node_permissions_apply() would (after25de7aa7b9) set uid=gid=0 if they weren't set by the rules. So let's only pass uid/gid/mode to node_permissions_apply() if appropriately configured. Also let node_permissions_apply() do the skip of uid/gid/mode if not set, and rename "always_apply" to more closely reflect its meaning.
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
Languages
C
88.5%
Shell
5.7%
Python
4.6%
Meson
1.1%