On Sun, Jul 28, 2024 at 16:43:01 +0200, Vincent Lefevre wrote:
> More or less. In the systemd case, for each file, either one chooses
> it, i.e. one has all the current defaults, or one chooses to provide
> a replacement under /etc, i.e. one entirely replaces the defaults by
> one's own settings. An include mechanism would allow a finer control
> of the settings. The sysctl.d configuration system does not allow one
> to include a file (to get the current defaults and possibly change
> some of them just after).
I really don't understand what you're asking for here.
There are defaults in /usr/lib/sysctl.d/*.conf (which is documented
in sysctl.d(5) even in bookworm). The files in /etc/sysctl.d/*.conf
will override those defaults.
Configuration files are read from directories in /etc/, /run/,
/usr/local/lib/, and /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
/lib/. Files in /run/ override files with the same name under /usr/.
Why do you need to see the literal word "include" in some other file?
What benefit does that give you?
