On Thu, May 9, 2024 at 5:59 PM Jon LaBadie <jo...@jgcomp.com> 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 <horsley1...@gmail.com> 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. Jeff
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
