Re: Who moved my journald.conf?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Thu, May 9, 2024 at 5:59 PM Jon LaBadie <jonfu@xxxxxxxxxx> wrote:
On Thu, May 09, 2024 at 03:45:54PM -0400, Jeffrey Walton wrote:
>On Thu, May 9, 2024 at 3:14 PM Tom Horsley <horsley1953@xxxxxxxxx> wrote:
>> On Thu, 9 May 2024 19:15:20 +0100
>> Barry Scott wrote:
>> >        All options are configured in the [Journal] section:
>> Yep, but it is concatenating all the different bits and pieces
>> it picks up from the journald.conf.d directory, so is the [Journal]
>> in the default file enough to imply [Journal] for all the pieces
>> it picks up from the directory? I mean, what if [Journal] means
>> "Forget everything, we're starting journal options now"? The last
>> thing you'd want to do is put in a [Journal] line in that case and
>> forget all the previous settings :-).
>> [Train of thought like this is what happens when a computer programmer
>> tries to read an ambiguous manual].
>When it comes to configuration using the .d/ directories, I believe it is a
>"sticky" scheme. The first time the option is set, it becomes sticky and it
>is not overridden later. That's why applications read .d/ configuration
>files first (and in a deterministic order, like 10-*.conf before 50-*.conf
>files), and then fallback to the package's or maintainer's configuration
>options for missing options.

"journald.conf(5) describes it differently.
Below I've broken up a single paragraph from that manpage.

   In addition to the "main" configuration file, drop-in configuration snippets
   are read from /usr/lib/systemd/*.conf.d/, /usr/local/lib/systemd/*.conf.d/,
   and /etc/systemd/*.conf.d/.  Those drop-ins have higher precedence and
   override the main configuration file.

So even if a line in the "main" config file is uncommentted, it value is
not "sticky".

   Files in the *.conf.d/ configuration subdirectories are sorted by their
   filename in lexicographic order, regardless of in which of the
   subdirectories they reside.

So with multiple drop-in config files, their name, not directory
location, determines the order read.

   When multiple files specify the same option, for options which accept
   just a single value, the entry in the file sorted last takes precedence,

So no option setting is sticky, it is last setting read rules.

   and for options which accept a list of values, entries are collected
   as they occur in the sorted files.

My bad, I stand corrected.

users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux