Bug 2444143

Summary: systemd package should own /etc/systemd/system.conf.d directory
Product: [Fedora] Fedora Reporter: Jaroslav Škarvada <jskarvad>
Component: systemdAssignee: systemd-maint
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: daan.j.demeyer, dtardon, fedoraproject, lnykryn, msekleta, suraj.ghimire7, systemd-maint, yuwatana, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-08-07 12:41:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jaroslav Škarvada 2026-03-03 18:39:22 UTC 
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.
Comment 1 David Tardon 2026-08-07 12:41:23 UTC 
(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.