From 809a2f59b30a1efc7cd07485a16deafeeee73447 Mon Sep 17 00:00:00 2001 From: Ina Panova Date: Fri, 25 Oct 2024 15:42:34 +0200 Subject: [PATCH] Add a more robust example of how config files are parsed. configuration_files_specification.md: show how configs are evaluated from different drop-in dirs in combination with colliding names and also having separate config files. Signed-off-by: Ina Panova --- specs/configuration_files_specification.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/specs/configuration_files_specification.md b/specs/configuration_files_specification.md index a88300e..3f33855 100644 --- a/specs/configuration_files_specification.md +++ b/specs/configuration_files_specification.md @@ -73,6 +73,17 @@ The configuration in `bar.conf` has the lowest priority, and is overridden by `a.conf` and `b.conf`. `b.conf` has the highest priority. +Here's another, more robust example. This is the order in which the files are parsed. +Note that files with the same name override each other: + +``` +/usr/lib/foo/bar.conf +/etc/foo/bar.conf (overrides /usr/lib/foo/bar.conf) +/usr/lib/foo/bar.conf.d/a.conf +/etc/foo/bar.conf.d/a.conf (/usr/lib/foo/bar.conf.d/a.conf) +/usr/lib/foo/bar.conf.d/b.conf +``` + If a config file is masked, drop-ins must still be parsed, unless they are masked themselves.