summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2019-01-18 16:34:45 +0100
committerLennart Poettering <lennart@poettering.net>2019-02-15 17:16:54 +0100
commitaa1f2e52e8445c8059c3793dfd779e2296eb5f2a (patch)
tree455f52e6c38c232fd7212d0763db42707d61228a /man
parent52b32b2aac96562ae8c380d8869b667f806471e0 (diff)
downloadsystemd-aa1f2e52e8445c8059c3793dfd779e2296eb5f2a.tar.gz
man: document the new BSD file lock logic in tmpfiles
Diffstat (limited to 'man')
-rw-r--r--man/tmpfiles.d.xml8
1 files changed, 8 insertions, 0 deletions
diff --git a/man/tmpfiles.d.xml b/man/tmpfiles.d.xml
index 3f2ef7ee97..e5ea2bec8b 100644
--- a/man/tmpfiles.d.xml
+++ b/man/tmpfiles.d.xml
@@ -545,6 +545,14 @@ w- /proc/sys/vm/swappiness - - - - 10</programlisting></para>
(ctime). Any of these three (or two) values will prevent cleanup
if it is more recent than the current time minus the age
field.</para>
+
+ <para>Note that while the aging algorithm is run a 'shared' BSD file lock (see <citerefentry
+ project='man-pages'><refentrytitle>flock</refentrytitle><manvolnum>2</manvolnum></citerefentry>) is
+ taken on each directory the algorithm descends into (and each directory below that, and so on). If the
+ aging algorithm finds a lock is already taken on some directory, it (and everything below it) is
+ skipped. Applications may use this to temporarily exclude certain directory subtrees from the aging
+ algorithm: the applications can take a BSD file lock themselves, and as long as they keep it aging of
+ the directory and everything below it is disabled.</para>
</refsect2>
<refsect2>