tmpfiles: clarify that "!" lines are filtered before collisions are checked
Fixes: #15675
This commit is contained in:
parent
f742f9d317
commit
ead2a4a231
|
@ -121,16 +121,19 @@ A+ /path-or-glob/to/append/acls/recursively - - - - POSIX
|
||||||
<filename>/usr/lib/tmpfiles.d</filename> and <filename>/run/tmpfiles.d</filename>. Files in
|
<filename>/usr/lib/tmpfiles.d</filename> and <filename>/run/tmpfiles.d</filename>. Files in
|
||||||
<filename>/run/tmpfiles.d</filename> override files with the same name in
|
<filename>/run/tmpfiles.d</filename> override files with the same name in
|
||||||
<filename>/usr/lib/tmpfiles.d</filename>. Packages should install their configuration files in
|
<filename>/usr/lib/tmpfiles.d</filename>. Packages should install their configuration files in
|
||||||
<filename>/usr/lib/tmpfiles.d</filename>. Files in <filename>/etc/tmpfiles.d</filename> are reserved for the local
|
<filename>/usr/lib/tmpfiles.d</filename>. Files in <filename>/etc/tmpfiles.d</filename> are reserved for
|
||||||
administrator, who may use this logic to override the configuration files installed by vendor packages. All
|
the local administrator, who may use this logic to override the configuration files installed by vendor
|
||||||
configuration files are sorted by their filename in lexicographic order, regardless of which of the directories
|
packages. All configuration files are sorted by their filename in lexicographic order, regardless of
|
||||||
they reside in. If multiple files specify the same path, the entry in the file with the lexicographically earliest
|
which of the directories they reside in. If multiple files specify the same path, the entry in the file
|
||||||
name will be applied. All other conflicting entries will be logged as errors. When two lines are prefix path and
|
with the lexicographically earliest name will be applied (note that lines suppressed due to the
|
||||||
suffix path of each other, then the prefix line is always created first, the suffix later (and if removal applies
|
<literal>!</literal> are filtered before application, meaning that if an early line carries the
|
||||||
to the line, the order is reversed: the suffix is removed first, the prefix later). Lines that take globs are
|
exclamation mark and is suppressed because of that, a later line matching in path will be applied). All
|
||||||
applied after those accepting no globs. If multiple operations shall be applied on the same file (such as ACL,
|
other conflicting entries will be logged as errors. When two lines are prefix path and suffix path of
|
||||||
xattr, file attribute adjustments), these are always done in the same fixed order. Except for those cases, the
|
each other, then the prefix line is always created first, the suffix later (and if removal applies to the
|
||||||
files/directories are processed in the order they are listed.</para>
|
line, the order is reversed: the suffix is removed first, the prefix later). Lines that take globs are
|
||||||
|
applied after those accepting no globs. If multiple operations shall be applied on the same file (such as
|
||||||
|
ACL, xattr, file attribute adjustments), these are always done in the same fixed order. Except for those
|
||||||
|
cases, the files/directories are processed in the order they are listed.</para>
|
||||||
|
|
||||||
<para>If the administrator wants to disable a configuration file
|
<para>If the administrator wants to disable a configuration file
|
||||||
supplied by the vendor, the recommended way is to place a symlink
|
supplied by the vendor, the recommended way is to place a symlink
|
||||||
|
|
Loading…
Reference in a new issue