From 2cb7e0aaedad73b076ea18c6900b0e86c5760d79 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 27 Apr 2024 15:00:47 +0200 Subject: Adding upstream version 247.3. Signed-off-by: Daniel Baumann --- man/standard-conf.xml | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 73 insertions(+) create mode 100644 man/standard-conf.xml (limited to 'man/standard-conf.xml') diff --git a/man/standard-conf.xml b/man/standard-conf.xml new file mode 100644 index 0000000..69cd7b0 --- /dev/null +++ b/man/standard-conf.xml @@ -0,0 +1,73 @@ + + + + + + + + Configuration Directories and Precedence + + Configuration files are read from directories in /etc/, + /run/, /usr/local/lib/, and /usr/lib/, in + order of precedence, as listed in the SYNOPSIS section above. Files must have the + .conf extension. Files in /etc/ override files with the same name + in /run/, /usr/local/lib/, and + /usr/lib/. Files in /run/ override files with the same name + under /usr/. + + All configuration files are sorted by their filename in lexicographic order, regardless of which of + the directories they reside in. If multiple files specify the same option, the entry in the file with the + lexicographically latest name will take precedence. Thus, the configuration in a certain file may either + be replaced completely (by placing a file with the same name in a directory with higher priority), or + individual settings might be changed (by specifying additional settings in a file with a different name + that is ordered later). + + Packages should install their configuration files in /usr/lib/ (distribution + packages) or /usr/local/lib/ (local installs). Files in /etc/ + are reserved for the local administrator, who may use this logic to override the configuration files + installed by vendor packages. It is recommended to prefix all filenames with a two-digit number and a + dash, to simplify the ordering of the files. + + If the administrator wants to disable a configuration file supplied by the vendor, the recommended + way is to place a symlink to /dev/null in the configuration directory in + /etc/, with the same filename as the vendor configuration file. If the vendor + configuration file is included in the initrd image, the image has to be regenerated. + + + + Configuration Directories and Precedence + + The default configuration is defined during compilation, so a + configuration file is only needed when it is necessary to deviate + from those defaults. By default, the configuration file in + /etc/systemd/ contains commented out entries + showing the defaults as a guide to the administrator. This file + can be edited to create local overrides. + + + When packages need to customize the configuration, they can install configuration snippets in + /usr/lib/systemd/*.conf.d/ or /usr/local/lib/systemd/*.conf.d/. + The main configuration file is read before any of the configuration directories, and has the lowest + precedence; entries in a file in any configuration directory override entries in the single configuration + file. Files in the *.conf.d/ configuration subdirectories are sorted by their + filename in lexicographic order, regardless of in which of the subdirectories they reside. When multiple + files specify the same option, for options which accept just a single value, the entry in the file with + the lexicographically latest name takes precedence. For options which accept a list of values, entries + are collected as they occur in files sorted lexicographically. + + Files in /etc/ are reserved for the local administrator, who may use this + logic to override the configuration files installed by vendor packages. It is recommended to prefix all + filenames in those subdirectories with a two-digit number and a dash, to simplify the ordering of the + files. + + To disable a configuration file supplied by the vendor, the + recommended way is to place a symlink to + /dev/null in the configuration directory in + /etc/, with the same filename as the vendor + configuration file. + + -- cgit v1.2.3