Fedora Account System
Red Hat Associate
Red Hat Customer
It already owns empty dirs in /etc like e.g. /etc/systemd/network, so it should also own the /etc/systemd/system.conf.d directory for drop-ins. Reproducible: Always Steps to Reproduce: 1. dnf provides /etc/systemd/system.conf.d 2. 3. Actual Results: No match Expected Results: Owned by systemd Additional Information: This complicates situations where some package needs to add drop-in there, it will have to also own/co-own the directory not to cause unowned directory. Well, packages should put drop-ins into /usr/lib/systemd/system.conf.d, but e.g. with TuneD we need to reconfigure the drop-in at runtime and need it to persist the reboot so the /usr/lib/systemd/system.conf.d or /run/systemd/system.conf.d/ maybe not suitable.
(In reply to Jaroslav Škarvada from comment #0) > It already owns empty dirs in /etc like e.g. /etc/systemd/network, so it > should also own the /etc/systemd/system.conf.d directory for drop-ins. This is a ghost of the past. systemd had to own some dirs in /etc/ because it actually installed config files there. These have all been moved into /usr/lib/systemd, but systemd %ghosts the original location to avoid removal (that is, rename to .rpmsave) of admin-changed files. That the dirs also continue to be owned by systemd is just a side-effect of that. But I'm pretty sure we shouldn't claim any new stuff in /etc, as it's viewed as admin territory these days. > This complicates situations where some package needs to add drop-in there, > it will have to also own/co-own the directory not to cause unowned directory. IMHO unowned dirs in /etc should be the rule unless they contain stuff actually installed by a package.