X-Git-Url: http://git.ipfire.org/?a=blobdiff_plain;f=man%2Ftmpfiles.d.xml;fp=man%2Ftmpfiles.d.xml;h=495315d55c60fc87b041eaeec66dc1ef628fe6ec;hb=dbc3cc8b832a7648f68b69e1322563d64cffd9c4;hp=ef0bb1f7f89bc4e3dad9e20afe26713128a03954;hpb=08c25eee3477aab83ac8f4d3237bc628c3ba2615;p=thirdparty%2Fsystemd.git

diff --git a/man/tmpfiles.d.xml b/man/tmpfiles.d.xml
index ef0bb1f7f89..495315d55c6 100644
--- a/man/tmpfiles.d.xml
+++ b/man/tmpfiles.d.xml
@@ -661,6 +661,14 @@ d /tmp/foo/bar - - - bmA:1h -</programlisting></para>
       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/file and everything below it is disabled.</para>
+
+      <para>This behavior can be used to ensure guaranteed cleanup of files or directories whose lifetime
+      should be aligned with the process that created them by having that process create them in a location
+      monitored by <command>systemd-tmpfiles</command> with an age of <literal>0</literal>, and having the
+      process immediately lock the directory or file before using it. Because the BSD lock is process
+      specific, the file is guaranteed to be unlocked as soon as the process exits, meaning that even if the
+      process crashes, those files and directories will be unlocked and cleaned up by
+      <command>systemd-tmpfiles</command>.</para>
     </refsect2>
 
     <refsect2>