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 <[email protected]>
uapi-group · Oct 25, 2024 · 809a2f5 · 809a2f5
1 parent 2d7f554
commit 809a2f5
Showing 1 changed file with 11 additions and 0 deletions.
diff --git 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.