On Fri, Aug 11, Manfred Hollstein wrote:
Moin,
to be honest, I'm afraid the whole UsrMerge activitiy told us something completely different!
No, it does not.
On Fri, 11 Aug 2023, 18:40:44 +0200, Franck Bui wrote:
Hi,
The way the systemd daemons (such as PID1, logind) parse their configuration file is specified in systemd-system.conf(5) man page (section CONFIGURATION DIRECTORIES AND PRECEDENCE).
Basically the daemons parse first their "main" configuration file (e.g /etc/systemd/system.conf for PID1) and then read and apply the optional drop-in files located in the following directories:
/usr/lib/systemd/*.conf.d/ /usr/local/lib/systemd/*.conf.d/ /run/systemd/*.conf.d/ /etc/systemd/*.conf.d/
*If* systemd (PID1) has access to /usr/lib/systemd/system.conf, it *must* use that file - unless there is a file /etc/systemd/system.conf.
During the process to migrate all /{bin,etc,lib}/* files, we were told to leave the file at /usr/* untouched and make our local modifications to the files at /etc/...
Now systemd wants to tell us a different logic :(
No, it is not about /usr/lib/systemd/system.conf vs /etc/systemd/system.conf, it is about the logic how to handle ".d" directories and snippets. You are mixing up two differnt things. Read the next sentence again:
It's important to note that drop-in files have higher precedence than the main configuration file. Hence if a package customizes an option by shipping a drop-in file in /usr/lib/systemd/*.conf.d/, it might override the value already set by the user if the same option was customized by the sysadmin in the main configuration.
Again, to be honest, we had a lot of effort and work to teach the various packages to be able to deal with two different configuration directories below /usr and /etc for overriding stuff, now systemd wants to revert that? I strongly vote NO!
No, systemd does not revert anything and none of our effords is void with this. Between, libeconf behaves in the same way with with drop-in files as systemd. And with drop-in files, the main configuration file should no longer be used at all. For other parts is already normal, or do you know anybody who is still using /etc/pam.conf? So systemd is only consequent here. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)