]>
Commit | Line | Data |
---|---|---|
514094f9 | 1 | <?xml version='1.0'?> |
3a54a157 ZJS |
2 | <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" |
3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> | |
4149f86d | 4 | <!-- |
db9ecf05 | 5 | SPDX-License-Identifier: LGPL-2.1-or-later |
572eb058 | 6 | |
96b2fb93 | 7 | Copyright © 2010 Brandon Philips |
4149f86d | 8 | --> |
503298b7 LP |
9 | <refentry id="tmpfiles.d" |
10 | xmlns:xi="http://www.w3.org/2001/XInclude"> | |
4149f86d | 11 | |
302fbdf2 ZJS |
12 | <refentryinfo> |
13 | <title>tmpfiles.d</title> | |
14 | <productname>systemd</productname> | |
302fbdf2 ZJS |
15 | </refentryinfo> |
16 | ||
17 | <refmeta> | |
18 | <refentrytitle>tmpfiles.d</refentrytitle> | |
19 | <manvolnum>5</manvolnum> | |
20 | </refmeta> | |
21 | ||
22 | <refnamediv> | |
23 | <refname>tmpfiles.d</refname> | |
24 | <refpurpose>Configuration for creation, deletion and cleaning of | |
25 | volatile and temporary files</refpurpose> | |
26 | </refnamediv> | |
27 | ||
28 | <refsynopsisdiv> | |
f2b5ca0e ZJS |
29 | <para><literallayout><filename>/etc/tmpfiles.d/*.conf</filename> |
30 | <filename>/run/tmpfiles.d/*.conf</filename> | |
31 | <filename>/usr/lib/tmpfiles.d/*.conf</filename> | |
32 | </literallayout></para> | |
33 | ||
34 | <para><literallayout><filename>~/.config/user-tmpfiles.d/*.conf</filename> | |
35 | <filename>$XDG_RUNTIME_DIR/user-tmpfiles.d/*.conf</filename> | |
36 | <filename>~/.local/share/user-tmpfiles.d/*.conf</filename> | |
f8b68539 | 37 | <filename index='false'>…</filename> |
f2b5ca0e ZJS |
38 | <filename>/usr/share/user-tmpfiles.d/*.conf</filename> |
39 | </literallayout></para> | |
b0458daf ZJS |
40 | |
41 | <programlisting>#Type Path Mode User Group Age Argument | |
42 | f /file/to/create mode user group - content | |
eccebf4b | 43 | f+ /file/to/create-or-truncate mode user group - content |
b0458daf | 44 | w /file/to/write-to - - - - content |
4b55952d | 45 | w+ /file/to/append-to - - - - content |
b0458daf ZJS |
46 | d /directory/to/create-and-cleanup mode user group cleanup-age - |
47 | D /directory/to/create-and-remove mode user group cleanup-age - | |
48 | e /directory/to/cleanup mode user group cleanup-age - | |
6f310287 KM |
49 | v /subvolume-or-directory/to/create mode user group cleanup-age - |
50 | q /subvolume-or-directory/to/create mode user group cleanup-age - | |
51 | Q /subvolume-or-directory/to/create mode user group cleanup-age - | |
b0458daf | 52 | p /fifo/to/create mode user group - - |
4b55952d | 53 | p+ /fifo/to/[re]create mode user group - - |
b0458daf | 54 | L /symlink/to/create - - - - symlink/target/path |
4b55952d | 55 | L+ /symlink/to/[re]create - - - - symlink/target/path |
f6bc26ee AB |
56 | c /dev/char-device-to-create mode user group - major:minor |
57 | c+ /dev/char-device-to-[re]create mode user group - major:minor | |
58 | b /dev/block-device-to-create mode user group - major:minor | |
59 | b+ /dev/block-device-to-[re]create mode user group - major:minor | |
6f310287 KM |
60 | C /target/to/create - - - cleanup-age /source/to/copy |
61 | x /path-or-glob/to/ignore/recursively - - - cleanup-age - | |
62 | X /path-or-glob/to/ignore - - - cleanup-age - | |
b0458daf ZJS |
63 | r /empty/dir/to/remove - - - - - |
64 | R /dir/to/remove/recursively - - - - - | |
d4ffda38 TM |
65 | z /path-or-glob/to/adjust/mode mode user group - - |
66 | Z /path-or-glob/to/adjust/mode/recursively mode user group - - | |
b0458daf ZJS |
67 | t /path-or-glob/to/set/xattrs - - - - xattrs |
68 | T /path-or-glob/to/set/xattrs/recursively - - - - xattrs | |
69 | h /path-or-glob/to/set/attrs - - - - file attrs | |
70 | H /path-or-glob/to/set/attrs/recursively - - - - file attrs | |
71 | a /path-or-glob/to/set/acls - - - - POSIX ACLs | |
4b55952d | 72 | a+ /path-or-glob/to/append/acls - - - - POSIX ACLs |
b0458daf | 73 | A /path-or-glob/to/set/acls/recursively - - - - POSIX ACLs |
4b55952d ZS |
74 | A+ /path-or-glob/to/append/acls/recursively - - - - POSIX ACLs |
75 | ||
b0458daf | 76 | </programlisting> |
302fbdf2 ZJS |
77 | </refsynopsisdiv> |
78 | ||
79 | <refsect1> | |
80 | <title>Description</title> | |
81 | ||
abcb67ce ZJS |
82 | <para><filename>tmpfiles.d</filename> configuration files provide a generic mechanism to define the |
83 | <emphasis>creation</emphasis> of regular files, directories, pipes, and device nodes, adjustments to | |
84 | their <emphasis>access mode, ownership, attributes, quota assignments, and contents</emphasis>, and | |
85 | finally their time-based <emphasis>removal</emphasis>. It is mostly commonly used for volatile and | |
3b121157 ZJS |
86 | temporary files and directories (such as those located under <filename>/run/</filename>, |
87 | <filename>/tmp/</filename>, <filename>/var/tmp/</filename>, the API file systems such as | |
88 | <filename>/sys/</filename> or <filename>/proc/</filename>, as well as some other directories below | |
89 | <filename>/var/</filename>).</para> | |
abcb67ce ZJS |
90 | |
91 | <para><command>systemd-tmpfiles</command> uses this configuration to create volatile files and | |
92 | directories during boot and to do periodic cleanup afterwards. See | |
93 | <citerefentry><refentrytitle>systemd-tmpfiles</refentrytitle><manvolnum>5</manvolnum></citerefentry> for | |
94 | the description of <filename>systemd-tmpfiles-setup.service</filename>, | |
6457e889 | 95 | <filename>systemd-tmpfiles-clean.service</filename>, and associated units.</para> |
abcb67ce | 96 | |
3b121157 | 97 | <para>System daemons frequently require private runtime directories below <filename>/run/</filename> to |
1cee1c52 | 98 | store communication sockets and similar. For these, it is better to use |
abcb67ce ZJS |
99 | <varname>RuntimeDirectory=</varname> in their unit files (see |
100 | <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry> for | |
101 | details), if the flexibility provided by <filename>tmpfiles.d</filename> is not required. The advantages | |
102 | are that the configuration required by the unit is centralized in one place, and that the lifetime of the | |
103 | directory is tied to the lifetime of the service itself. Similarly, <varname>StateDirectory=</varname>, | |
104 | <varname>CacheDirectory=</varname>, <varname>LogsDirectory=</varname>, and | |
105 | <varname>ConfigurationDirectory=</varname> should be used to create directories under | |
106 | <filename>/var/lib/</filename>, <filename>/var/cache/</filename>, <filename>/var/log/</filename>, and | |
107 | <filename>/etc/</filename>. <filename>tmpfiles.d</filename> should be used for files whose lifetime is | |
108 | independent of any service or requires more complicated configuration.</para> | |
302fbdf2 ZJS |
109 | </refsect1> |
110 | ||
111 | <refsect1> | |
8165be2e | 112 | <title>Configuration Directories and Precedence</title> |
302fbdf2 ZJS |
113 | |
114 | <para>Each configuration file shall be named in the style of | |
115 | <filename><replaceable>package</replaceable>.conf</filename> or | |
116 | <filename><replaceable>package</replaceable>-<replaceable>part</replaceable>.conf</filename>. | |
117 | The second variant should be used when it is desirable to make it | |
118 | easy to override just this part of configuration.</para> | |
119 | ||
ad19c578 LP |
120 | <para>Files in <filename>/etc/tmpfiles.d</filename> override files with the same name in |
121 | <filename>/usr/lib/tmpfiles.d</filename> and <filename>/run/tmpfiles.d</filename>. Files in | |
122 | <filename>/run/tmpfiles.d</filename> override files with the same name in | |
123 | <filename>/usr/lib/tmpfiles.d</filename>. Packages should install their configuration files in | |
ead2a4a2 LP |
124 | <filename>/usr/lib/tmpfiles.d</filename>. Files in <filename>/etc/tmpfiles.d</filename> are reserved for |
125 | the local administrator, who may use this logic to override the configuration files installed by vendor | |
126 | packages. All configuration files are sorted by their filename in lexicographic order, regardless of | |
127 | which of the directories they reside in. If multiple files specify the same path, the entry in the file | |
128 | with the lexicographically earliest name will be applied (note that lines suppressed due to the | |
129 | <literal>!</literal> are filtered before application, meaning that if an early line carries the | |
130 | exclamation mark and is suppressed because of that, a later line matching in path will be applied). All | |
131 | other conflicting entries will be logged as errors. When two lines are prefix path and suffix path of | |
132 | each other, then the prefix line is always created first, the suffix later (and if removal applies to the | |
133 | line, the order is reversed: the suffix is removed first, the prefix later). Lines that take globs are | |
134 | applied after those accepting no globs. If multiple operations shall be applied on the same file (such as | |
135 | ACL, xattr, file attribute adjustments), these are always done in the same fixed order. Except for those | |
136 | cases, the files/directories are processed in the order they are listed.</para> | |
302fbdf2 ZJS |
137 | |
138 | <para>If the administrator wants to disable a configuration file | |
139 | supplied by the vendor, the recommended way is to place a symlink | |
140 | to <filename>/dev/null</filename> in | |
141 | <filename>/etc/tmpfiles.d/</filename> bearing the same filename. | |
142 | </para> | |
8165be2e ZJS |
143 | </refsect1> |
144 | ||
145 | <refsect1> | |
146 | <title>Configuration File Format</title> | |
302fbdf2 | 147 | |
29271da5 LP |
148 | <para>The configuration format is one line per path, containing type, path, mode, ownership, age, and |
149 | argument fields. The lines are separated by newlines, the fields by whitespace:</para> | |
302fbdf2 | 150 | |
29271da5 | 151 | <programlisting>#Type Path Mode User Group Age Argument… |
488e4352 ZJS |
152 | d /run/user 0755 root root 10d - |
153 | L /tmp/foobar - - - - /dev/null</programlisting> | |
302fbdf2 | 154 | |
29271da5 LP |
155 | <para>Fields may contain C-style escapes. With the exception of the seventh field (the "argument") all |
156 | fields may be enclosed in quotes. Note that any whitespace found in the line after the beginning of the | |
157 | argument field will be considered part of the argument field. To begin the argument field with a | |
158 | whitespace character, use C-style escapes (e.g. <literal>\x20</literal>).</para> | |
657cf7f4 | 159 | |
302fbdf2 ZJS |
160 | <refsect2> |
161 | <title>Type</title> | |
162 | ||
e52f6f63 LP |
163 | <para>The type consists of a single letter and optionally one or emore modifier characters: a plus sign |
164 | (<literal>+</literal>), exclamation mark (<literal>!</literal>), minus sign (<literal>-</literal>), | |
165 | equals sign (<literal>=</literal>), tilde character (<literal>~</literal>) and/or caret | |
166 | (<literal>^</literal>).</para> | |
302fbdf2 ZJS |
167 | |
168 | <para>The following line types are understood:</para> | |
169 | ||
170 | <variablelist> | |
171 | <varlistentry> | |
172 | <term><varname>f</varname></term> | |
eccebf4b ZS |
173 | <term><varname>f+</varname></term> |
174 | <listitem><para><varname>f</varname> will create a file if it does not exist yet. If the argument | |
175 | parameter is given and the file did not exist yet, it will be written to the file. | |
176 | <varname>f+</varname> will create or truncate the file. If the argument parameter is given, it will | |
177 | be written to the file. Does not follow symlinks.</para></listitem> | |
302fbdf2 ZJS |
178 | </varlistentry> |
179 | ||
180 | <varlistentry> | |
eccebf4b ZS |
181 | <term><varname>w</varname></term> |
182 | <term><varname>w+</varname></term> | |
d0ea5c5e ZS |
183 | <listitem><para>Write the argument parameter to a file, if the file exists. |
184 | If suffixed with <varname>+</varname>, the line will be appended to the file. | |
185 | If your configuration writes multiple lines to the same file, use <varname>w+</varname>. | |
186 | Lines of this type accept shell-style globs in place of normal path names. | |
187 | The argument parameter will be written without a trailing newline. | |
188 | C-style backslash escapes are interpreted. Follows symlinks.</para></listitem> | |
302fbdf2 ZJS |
189 | </varlistentry> |
190 | ||
191 | <varlistentry> | |
192 | <term><varname>d</varname></term> | |
488e4352 ZJS |
193 | <listitem><para>Create a directory. The mode and ownership will be adjusted if specified. Contents |
194 | of this directory are subject to time based cleanup if the age argument is specified. | |
195 | </para></listitem> | |
302fbdf2 ZJS |
196 | </varlistentry> |
197 | ||
198 | <varlistentry> | |
199 | <term><varname>D</varname></term> | |
488e4352 ZJS |
200 | <listitem><para>Similar to <varname>d</varname>, but in addition the contents of the directory will |
201 | be removed when <option>--remove</option> is used.</para></listitem> | |
4b743d67 | 202 | </varlistentry> |
df8dee85 ZJS |
203 | |
204 | <varlistentry> | |
205 | <term><varname>e</varname></term> | |
488e4352 ZJS |
206 | <listitem><para>Adjust the mode and ownership of existing directories and remove their contents |
207 | based on age. | |
208 | Lines of this type accept shell-style globs in place of normal path names. Contents of the | |
209 | directories are subject to time based cleanup if the age argument is specified. If the age argument | |
210 | is <literal>0</literal>, contents will be unconditionally deleted every time | |
211 | <command>systemd-tmpfiles --clean</command> is run.</para> | |
212 | ||
213 | <para>For this entry to be useful, at least one of the mode, user, group, or age arguments must be | |
214 | specified, since otherwise this entry has no effect. As an exception, an entry with no effect may | |
215 | be useful when combined with <varname>!</varname>, see the examples.</para></listitem> | |
302fbdf2 ZJS |
216 | </varlistentry> |
217 | ||
218 | <varlistentry> | |
219 | <term><varname>v</varname></term> | |
488e4352 ZJS |
220 | <listitem><para>Create a subvolume if the path does not exist yet, the file system supports |
221 | subvolumes (btrfs), and the system itself is installed into a subvolume (specifically: the root | |
222 | directory <filename>/</filename> is itself a subvolume). Otherwise, create a normal directory, in | |
223 | the same way as <varname>d</varname>.</para> | |
224 | ||
225 | <para>A subvolume created with this line type is not assigned to any higher-level quota group. For | |
226 | that, use <varname>q</varname> or <varname>Q</varname>, which allow creating simple quota group | |
227 | hierarchies, see below.</para></listitem> | |
5fb13eb5 LP |
228 | </varlistentry> |
229 | ||
230 | <varlistentry> | |
231 | <term><varname>q</varname></term> | |
488e4352 ZJS |
232 | <listitem><para>Create a subvolume or directory the same as <varname>v</varname>, but assign the |
233 | subvolume to the same higher-level quota groups as the parent. This ensures that higher-level | |
234 | limits and accounting applied to the parent subvolume also include the specified subvolume. On | |
235 | non-btrfs file systems, this line type is identical to <varname>d</varname>.</para> | |
f17a8d61 FB |
236 | |
237 | <para>If the subvolume already exists, no change to the quota hierarchy is made, regardless of whether the | |
238 | subvolume is already attached to a quota group or not. Also see <varname>Q</varname> below. See <citerefentry | |
239 | project='die-net'><refentrytitle>btrfs-qgroup</refentrytitle><manvolnum>8</manvolnum></citerefentry> for | |
240 | details about the btrfs quota group concept.</para></listitem> | |
5fb13eb5 LP |
241 | </varlistentry> |
242 | ||
243 | <varlistentry> | |
244 | <term><varname>Q</varname></term> | |
488e4352 ZJS |
245 | <listitem><para>Create the subvolume or directory the same as <varname>v</varname>, but assign the |
246 | new subvolume to a new leaf quota group. Instead of copying the higher-level quota group | |
247 | assignments from the parent as is done with <varname>q</varname>, the lowest quota group of the | |
248 | parent subvolume is determined that is not the leaf quota group. Then, an "intermediary" quota | |
249 | group is inserted that is one level below this level, and shares the same ID part as the specified | |
250 | subvolume. If no higher-level quota group exists for the parent subvolume, a new quota group at | |
251 | level 255 sharing the same ID as the specified subvolume is inserted instead. This new intermediary | |
252 | quota group is then assigned to the parent subvolume's higher-level quota groups, and the specified | |
253 | subvolume's leaf quota group is assigned to it.</para> | |
f17a8d61 FB |
254 | |
255 | <para>Effectively, this has a similar effect as <varname>q</varname>, however introduces a new higher-level | |
256 | quota group for the specified subvolume that may be used to enforce limits and accounting to the specified | |
257 | subvolume and children subvolume created within it. Thus, by creating subvolumes only via | |
258 | <varname>q</varname> and <varname>Q</varname>, a concept of "subtree quotas" is implemented. Each subvolume | |
259 | for which <varname>Q</varname> is set will get a "subtree" quota group created, and all child subvolumes | |
260 | created within it will be assigned to it. Each subvolume for which <varname>q</varname> is set will not get | |
261 | such a "subtree" quota group, but it is ensured that they are added to the same "subtree" quota group as | |
262 | their immediate parents.</para> | |
263 | ||
264 | <para>It is recommended to use <varname>Q</varname> for subvolumes that typically contain further subvolumes, | |
265 | and where it is desirable to have accounting and quota limits on all child subvolumes together. Examples for | |
3b121157 | 266 | <varname>Q</varname> are typically <filename>/home/</filename> or <filename>/var/lib/machines/</filename>. In |
f17a8d61 FB |
267 | contrast, <varname>q</varname> should be used for subvolumes that either usually do not include further |
268 | subvolumes or where no accounting and quota limits are needed that apply to all child subvolumes | |
3b121157 ZJS |
269 | together. Examples for <varname>q</varname> are typically <filename>/var/</filename> or |
270 | <filename>/var/tmp/</filename>. </para> | |
f17a8d61 FB |
271 | |
272 | <para>As with <varname>q</varname>, <varname>Q</varname> has no effect on the quota group hierarchy if the | |
488e4352 ZJS |
273 | subvolume already exists, regardless of whether the subvolume already belong to a quota group or not. |
274 | </para></listitem> | |
302fbdf2 ZJS |
275 | </varlistentry> |
276 | ||
277 | <varlistentry> | |
278 | <term><varname>p</varname></term> | |
279 | <term><varname>p+</varname></term> | |
280 | <listitem><para>Create a named pipe (FIFO) if it does not | |
281 | exist yet. If suffixed with <varname>+</varname> and a file | |
282 | already exists where the pipe is to be created, it will be | |
283 | removed and be replaced by the pipe.</para></listitem> | |
284 | </varlistentry> | |
285 | ||
286 | <varlistentry> | |
287 | <term><varname>L</varname></term> | |
288 | <term><varname>L+</varname></term> | |
289 | <listitem><para>Create a symlink if it does not exist | |
b3f5897f WD |
290 | yet. If suffixed with <varname>+</varname> and a file or |
291 | directory already exists where the symlink is to be created, | |
292 | it will be removed and be replaced by the symlink. If the | |
293 | argument is omitted, symlinks to files with the same name | |
294 | residing in the directory | |
295 | <filename>/usr/share/factory/</filename> are created. Note | |
296 | that permissions and ownership on symlinks are ignored. | |
297 | </para></listitem> | |
302fbdf2 ZJS |
298 | </varlistentry> |
299 | ||
300 | <varlistentry> | |
301 | <term><varname>c</varname></term> | |
302 | <term><varname>c+</varname></term> | |
303 | <listitem><para>Create a character device node if it does | |
304 | not exist yet. If suffixed with <varname>+</varname> and a | |
305 | file already exists where the device node is to be created, | |
306 | it will be removed and be replaced by the device node. It is | |
307 | recommended to suffix this entry with an exclamation mark to | |
308 | only create static device nodes at boot, as udev will not | |
309 | manage static device nodes that are created at runtime. | |
310 | </para></listitem> | |
311 | </varlistentry> | |
312 | ||
313 | <varlistentry> | |
314 | <term><varname>b</varname></term> | |
315 | <term><varname>b+</varname></term> | |
316 | <listitem><para>Create a block device node if it does not | |
317 | exist yet. If suffixed with <varname>+</varname> and a file | |
318 | already exists where the device node is to be created, it | |
319 | will be removed and be replaced by the device node. It is | |
320 | recommended to suffix this entry with an exclamation mark to | |
321 | only create static device nodes at boot, as udev will not | |
322 | manage static device nodes that are created at runtime. | |
323 | </para></listitem> | |
324 | </varlistentry> | |
325 | ||
326 | <varlistentry> | |
327 | <term><varname>C</varname></term> | |
328 | <listitem><para>Recursively copy a file or directory, if the | |
a6f44645 RG |
329 | destination files or directories do not exist yet or the |
330 | destination directory is empty. Note that this command will not | |
331 | descend into subdirectories if the destination directory already | |
332 | exists and is not empty. Instead, the entire copy operation is | |
333 | skipped. If the argument is omitted, files from the source directory | |
302fbdf2 | 334 | <filename>/usr/share/factory/</filename> with the same name |
708daf42 | 335 | are copied. Does not follow symlinks. Contents of the directories |
4da5e566 KM |
336 | are subject to time based cleanup if the age argument is specified. |
337 | </para></listitem> | |
302fbdf2 ZJS |
338 | </varlistentry> |
339 | ||
340 | <varlistentry> | |
341 | <term><varname>x</varname></term> | |
342 | <listitem><para>Ignore a path during cleaning. Use this type | |
343 | to exclude paths from clean-up as controlled with the Age | |
344 | parameter. Note that lines of this type do not influence the | |
345 | effect of <varname>r</varname> or <varname>R</varname> | |
50d9e46d | 346 | lines. Lines of this type accept shell-style globs in place |
302fbdf2 ZJS |
347 | of normal path names. </para></listitem> |
348 | </varlistentry> | |
349 | ||
350 | <varlistentry> | |
351 | <term><varname>X</varname></term> | |
352 | <listitem><para>Ignore a path during cleaning. Use this type | |
353 | to exclude paths from clean-up as controlled with the Age | |
354 | parameter. Unlike <varname>x</varname>, this parameter will | |
355 | not exclude the content if path is a directory, but only | |
356 | directory itself. Note that lines of this type do not | |
357 | influence the effect of <varname>r</varname> or | |
50d9e46d | 358 | <varname>R</varname> lines. Lines of this type accept |
302fbdf2 ZJS |
359 | shell-style globs in place of normal path names. |
360 | </para></listitem> | |
361 | </varlistentry> | |
362 | ||
363 | <varlistentry> | |
364 | <term><varname>r</varname></term> | |
365 | <listitem><para>Remove a file or directory if it exists. | |
366 | This may not be used to remove non-empty directories, use | |
367 | <varname>R</varname> for that. Lines of this type accept | |
368 | shell-style globs in place of normal path | |
6a9171d2 | 369 | names. Does not follow symlinks.</para></listitem> |
302fbdf2 ZJS |
370 | </varlistentry> |
371 | ||
372 | <varlistentry> | |
373 | <term><varname>R</varname></term> | |
374 | <listitem><para>Recursively remove a path and all its | |
375 | subdirectories (if it is a directory). Lines of this type | |
376 | accept shell-style globs in place of normal path | |
6a9171d2 | 377 | names. Does not follow symlinks.</para></listitem> |
302fbdf2 ZJS |
378 | </varlistentry> |
379 | ||
380 | <varlistentry> | |
381 | <term><varname>z</varname></term> | |
488e4352 ZJS |
382 | <listitem><para>Adjust the access mode, user and group ownership, and restore the SELinux security |
383 | context of a file or directory, if it exists. Lines of this type accept shell-style globs in place | |
384 | of normal path names. Does not follow symlinks.</para></listitem> | |
302fbdf2 ZJS |
385 | </varlistentry> |
386 | ||
387 | <varlistentry> | |
388 | <term><varname>Z</varname></term> | |
488e4352 ZJS |
389 | <listitem><para>Recursively set the access mode, user and group ownership, and restore the SELinux |
390 | security context of a file or directory if it exists, as well as of its subdirectories and the | |
391 | files contained therein (if applicable). Lines of this type accept shell-style globs in place of | |
392 | normal path names. Does not follow symlinks.</para></listitem> | |
302fbdf2 ZJS |
393 | </varlistentry> |
394 | ||
395 | <varlistentry> | |
396 | <term><varname>t</varname></term> | |
f3d3a9ca LP |
397 | <listitem><para>Set extended attributes, see <citerefentry |
398 | project='man-pages'><refentrytitle>attr</refentrytitle> | |
399 | <manvolnum>5</manvolnum></citerefentry> for details. The argument field should take one or more | |
400 | assignment expressions in the form | |
401 | <replaceable>namespace</replaceable>.<replaceable>attribute</replaceable>=<replaceable>value</replaceable>, | |
402 | for examples see below. Lines of this type accept shell-style globs in place of normal path | |
403 | names. This can be useful for setting SMACK labels. Does not follow symlinks.</para> | |
404 | ||
405 | <para>Please note that extended attributes settable with this line type are a different concept | |
406 | from the Linux file attributes settable with <varname>h</varname>/<varname>H</varname>, see | |
407 | below.</para></listitem> | |
b705ab6a ZJS |
408 | </varlistentry> |
409 | ||
410 | <varlistentry> | |
411 | <term><varname>T</varname></term> | |
f3d3a9ca | 412 | <listitem><para>Same as <varname>t</varname>, but operates recursively.</para></listitem> |
302fbdf2 | 413 | </varlistentry> |
f8eeeaf9 | 414 | |
fa3f5fd2 GB |
415 | <varlistentry> |
416 | <term><varname>h</varname></term> | |
f3d3a9ca LP |
417 | <listitem><para>Set Linux file/directory attributes. Lines of this type accept shell-style globs in |
418 | place of normal path names.</para> | |
fa3f5fd2 | 419 | |
f3d3a9ca | 420 | <para>The format of the argument field is <varname>[+-=][aAcCdDeijPsStTu]</varname>. The prefix |
75006470 LP |
421 | <varname>+</varname> (the default one) causes the attribute(s) to be added; <varname>-</varname> |
422 | causes the attribute(s) to be removed; <varname>=</varname> causes the attributes to be set exactly | |
423 | as the following letters. The letters <literal>aAcCdDeijPsStTu</literal> select the new attributes | |
424 | for the files, see <citerefentry project='man-pages'><refentrytitle>chattr</refentrytitle> | |
fa3f5fd2 GB |
425 | <manvolnum>1</manvolnum></citerefentry> for further information. |
426 | </para> | |
f3d3a9ca LP |
427 | |
428 | <para>Passing only <varname>=</varname> as argument resets all the file attributes listed above. It | |
429 | has to be pointed out that the <varname>=</varname> prefix limits itself to the attributes | |
430 | corresponding to the letters listed here. All other attributes will be left untouched. Does not | |
431 | follow symlinks.</para> | |
432 | ||
433 | <para>Please note that the Linux file attributes settable with this line type are a different | |
434 | concept from the extended attributes settable with <varname>t</varname>/<varname>T</varname>, | |
435 | see above.</para></listitem> | |
fa3f5fd2 GB |
436 | </varlistentry> |
437 | ||
438 | <varlistentry> | |
439 | <term><varname>H</varname></term> | |
f3d3a9ca | 440 | <listitem><para>Sames as <varname>h</varname>, but operates recursively.</para></listitem> |
fa3f5fd2 GB |
441 | </varlistentry> |
442 | ||
f8eeeaf9 ZJS |
443 | <varlistentry> |
444 | <term><varname>a</varname></term> | |
50d9e46d | 445 | <term><varname>a+</varname></term> |
f3d3a9ca LP |
446 | <listitem><para>Set POSIX ACLs (access control lists), see <citerefentry |
447 | project='man-pages'><refentrytitle>acl</refentrytitle> | |
448 | <manvolnum>5</manvolnum></citerefentry>. If suffixed with <varname>+</varname>, the specified | |
449 | entries will be added to the existing set. <command>systemd-tmpfiles</command> will automatically | |
450 | add the required base entries for user and group based on the access mode of the file, unless base | |
451 | entries already exist or are explicitly specified. The mask will be added if not specified | |
452 | explicitly or already present. Lines of this type accept shell-style globs in place of normal path | |
453 | names. This can be useful for allowing additional access to certain files. Does not follow | |
454 | symlinks.</para></listitem> | |
b705ab6a ZJS |
455 | </varlistentry> |
456 | ||
457 | <varlistentry> | |
458 | <term><varname>A</varname></term> | |
50d9e46d ZJS |
459 | <term><varname>A+</varname></term> |
460 | <listitem><para>Same as <varname>a</varname> and | |
6a9171d2 LP |
461 | <varname>a+</varname>, but recursive. Does not follow |
462 | symlinks.</para></listitem> | |
f8eeeaf9 | 463 | </varlistentry> |
302fbdf2 | 464 | </variablelist> |
67ff6b30 LP |
465 | </refsect2> |
466 | ||
467 | <refsect2> | |
468 | <title>Type Modifiers</title> | |
302fbdf2 | 469 | |
f742f9d3 LP |
470 | <para>If the exclamation mark (<literal>!</literal>) is used, this line is only safe to execute during |
471 | boot, and can break a running system. Lines without the exclamation mark are presumed to be safe to | |
472 | execute at any time, e.g. on package upgrades. <command>systemd-tmpfiles</command> will take lines with | |
473 | an exclamation mark only into consideration, if the <option>--boot</option> option is given.</para> | |
302fbdf2 ZJS |
474 | |
475 | <para>For example: | |
476 | <programlisting># Make sure these are created by default so that nobody else can | |
9b9c30ec | 477 | d /tmp/.X11-unix 1777 root root 10d |
302fbdf2 | 478 | |
9b9c30ec LP |
479 | # Unlink the X11 lock files |
480 | r! /tmp/.X[0-9]*-lock</programlisting> | |
302fbdf2 ZJS |
481 | The second line in contrast to the first one would break a |
482 | running system, and will only be executed with | |
483 | <option>--boot</option>.</para> | |
7fa10748 | 484 | |
f742f9d3 LP |
485 | <para>If the minus sign (<literal>-</literal>) is used, this line failing to run successfully during |
486 | create (and only create) will not cause the execution of <command>systemd-tmpfiles</command> to return | |
6d7b5433 WD |
487 | an error.</para> |
488 | ||
489 | <para>For example: | |
490 | <programlisting># Modify sysfs but don't fail if we are in a container with a read-only /proc | |
491 | w- /proc/sys/vm/swappiness - - - - 10</programlisting></para> | |
492 | ||
c46c3233 AW |
493 | <para>If the equals sign (<literal>=</literal>) is used, the file types of existing objects in the specified path |
494 | are checked, and removed if they do not match. This includes any implicitly created parent directories (which can | |
495 | be either directories or directory symlinks). For example, if there is a FIFO in place of one of the parent path | |
496 | components it will be replaced with a directory.</para> | |
497 | ||
708daf42 LP |
498 | <para>If the tilde character (<literal>~</literal>) is used, the argument (i.e. 6th) column is <ulink |
499 | url="https://www.rfc-editor.org/rfc/rfc4648.html">Base64 decoded</ulink> before use. This modifier is | |
500 | only supported on line types that can write file contents, i.e. <varname>f</varname>, | |
e52f6f63 LP |
501 | <varname>f+</varname>, <varname>w</varname>, <varname>+</varname>. This is useful for writing arbitrary |
502 | binary data (including newlines and NUL bytes) to files. Note that if this switch is used, the argument | |
503 | is not subject to specifier expansion, neither before nor after Base64 decoding.</para> | |
504 | ||
505 | <para>If the caret character (<literal>^</literal>) is used, the argument (i.e. 6th) column takes a | |
506 | service credential name to read the argument data from. See <ulink | |
507 | url="https://systemd.io/CREDENTIALS">System and Service Credentials</ulink> for details about the | |
508 | credentials concept. This modifier is only supported on line types that can write file contents, | |
509 | i.e. <varname>f</varname>, <varname>f+</varname>, <varname>w</varname>, <varname>w+</varname>. This is | |
510 | useful for writing arbitrary files with contents sourced from elsewhere, including from VM or container | |
511 | managers further up. If the specified credential is not set for the <command>systemd-tmpfiles</command> | |
512 | service, the line is silently skipped. If <literal>^</literal> and <literal>~</literal> are combined | |
513 | Base64 decoding is applied to the credential contents.</para> | |
708daf42 | 514 | |
7fa10748 LP |
515 | <para>Note that for all line types that result in creation of any kind of file node |
516 | (i.e. <varname>f</varname>/<varname>F</varname>, | |
517 | <varname>d</varname>/<varname>D</varname>/<varname>v</varname>/<varname>q</varname>/<varname>Q</varname>, | |
518 | <varname>p</varname>, <varname>L</varname>, <varname>c</varname>/<varname>b</varname> and <varname>C</varname>) | |
519 | leading directories are implicitly created if needed, owned by root with an access mode of 0755. In order to | |
520 | create them with different modes or ownership make sure to add appropriate <varname>d</varname> lines.</para> | |
302fbdf2 ZJS |
521 | </refsect2> |
522 | ||
523 | <refsect2> | |
524 | <title>Path</title> | |
525 | ||
526 | <para>The file system path specification supports simple | |
2df36d09 ZJS |
527 | specifier expansion, see below. The path (after expansion) must be |
528 | absolute.</para> | |
302fbdf2 ZJS |
529 | </refsect2> |
530 | ||
531 | <refsect2> | |
532 | <title>Mode</title> | |
533 | ||
fdc4b8b1 LP |
534 | <para>The file access mode to use when creating this file or directory. If omitted or when set to |
535 | <literal>-</literal>, the default is used: 0755 for directories, 0644 for all other file objects. For | |
536 | <varname>z</varname>, <varname>Z</varname> lines, if omitted or when set to <literal>-</literal>, the | |
537 | file access mode will not be modified. This parameter is ignored for <varname>x</varname>, | |
538 | <varname>r</varname>, <varname>R</varname>, <varname>L</varname>, <varname>t</varname>, and | |
539 | <varname>a</varname> lines.</para> | |
540 | ||
541 | <para>Optionally, if prefixed with <literal>~</literal>, the access mode is masked based on the already | |
542 | set access bits for existing file or directories: if the existing file has all executable bits unset, | |
543 | all executable bits are removed from the new access mode, too. Similarly, if all read bits are removed | |
544 | from the old access mode, they will be removed from the new access mode too, and if all write bits are | |
545 | removed, they will be removed from the new access mode too. In addition, the sticky/SUID/SGID bit is | |
546 | removed unless applied to a directory. This functionality is particularly useful in conjunction with | |
547 | <varname>Z</varname>.</para> | |
548 | ||
549 | <para>Optionally, if prefixed with <literal>:</literal>, the configured access mode is only used when | |
550 | creating new inodes. If the inode the line refers to already exists, its access mode is left in place | |
551 | unmodified.</para> | |
302fbdf2 ZJS |
552 | </refsect2> |
553 | ||
554 | <refsect2> | |
488e4352 ZJS |
555 | <title>User, Group</title> |
556 | ||
557 | <para>The user and group to use for this file or directory. This may either be a numeric ID or a | |
558 | user/group name. If omitted or when set to <literal>-</literal>, the user and group of the user who | |
559 | invokes <command>systemd-tmpfiles</command> is used. For <varname>z</varname> and <varname>Z</varname> | |
560 | lines, when omitted or when set to <literal>-</literal>, the file ownership will not be modified. These | |
561 | parameters are ignored for <varname>x</varname>, <varname>r</varname>, <varname>R</varname>, | |
562 | <varname>L</varname>, <varname>t</varname>, and <varname>a</varname> lines.</para> | |
007b77ac LP |
563 | |
564 | <para>This field should generally only reference system users/groups, i.e. users/groups that are | |
565 | guaranteed to be resolvable during early boot. If this field references users/groups that only become | |
566 | resolveable during later boot (i.e. after NIS, LDAP or a similar networked directory service become | |
567 | available), execution of the operations declared by the line will likely fail. Also see <ulink | |
d59fc29b | 568 | url="https://systemd.io/UIDS-GIDS/#notes-on-resolvability-of-user-and-group-names">Notes on |
007b77ac LP |
569 | Resolvability of User and Group Names</ulink> for more information on requirements on system user/group |
570 | definitions.</para> | |
fdc4b8b1 LP |
571 | |
572 | <para>Optionally, if prefixed with <literal>:</literal>, the configured user/group information is only | |
573 | used when creating new inodes. If the inode the line refers to already exists, its user/group is left | |
574 | in place unmodified.</para> | |
302fbdf2 ZJS |
575 | </refsect2> |
576 | ||
577 | <refsect2> | |
578 | <title>Age</title> | |
dab1fe1a | 579 | |
302fbdf2 ZJS |
580 | <para>The date field, when set, is used to decide what files to |
581 | delete when cleaning. If a file or directory is older than the | |
582 | current time minus the age field, it is deleted. The field | |
583 | format is a series of integers each followed by one of the | |
a8eaaee7 | 584 | following suffixes for the respective time units: |
00c53f42 ZJS |
585 | <constant>s</constant>, |
586 | <constant>m</constant> or <constant>min</constant>, | |
587 | <constant>h</constant>, | |
588 | <constant>d</constant>, | |
589 | <constant>w</constant>, | |
a8eaaee7 | 590 | <constant>ms</constant>, and |
00c53f42 | 591 | <constant>us</constant>, |
a8eaaee7 JE |
592 | meaning seconds, minutes, hours, days, weeks, |
593 | milliseconds, and microseconds, respectively. Full names of the time units can | |
00c53f42 ZJS |
594 | be used too. |
595 | </para> | |
302fbdf2 ZJS |
596 | |
597 | <para>If multiple integers and units are specified, the time | |
00c53f42 ZJS |
598 | values are summed. If an integer is given without a unit, |
599 | <constant>s</constant> is assumed. | |
302fbdf2 ZJS |
600 | </para> |
601 | ||
602 | <para>When the age is set to zero, the files are cleaned | |
603 | unconditionally.</para> | |
604 | ||
5fb13eb5 | 605 | <para>The age field only applies to lines starting with |
df8dee85 | 606 | <varname>d</varname>, <varname>D</varname>, <varname>e</varname>, |
5fb13eb5 LP |
607 | <varname>v</varname>, <varname>q</varname>, |
608 | <varname>Q</varname>, <varname>C</varname>, <varname>x</varname> | |
609 | and <varname>X</varname>. If omitted or set to | |
610 | <literal>-</literal>, no automatic clean-up is done.</para> | |
302fbdf2 | 611 | |
dab1fe1a ZJS |
612 | <para>If the age field starts with a tilde character <literal>~</literal>, clean-up is only applied to |
613 | files and directories one level inside the directory specified, but not the files and directories | |
614 | immediately inside it.</para> | |
662b3e58 LW |
615 | |
616 | <para>The age of a file system entry is determined from its last | |
617 | modification timestamp (mtime), its last access timestamp (atime), | |
618 | and (except for directories) its last status change timestamp | |
7f7a50dd SK |
619 | (ctime). By default, any of these three (or two) values will |
620 | prevent cleanup if it is more recent than the current time minus | |
621 | the age field. To restrict the deletion based on particular type | |
622 | of file timestamps, the age-by argument can be used.</para> | |
623 | ||
dab1fe1a ZJS |
624 | <para>The age-by argument overrides the timestamp types to be used for the age check. It can be |
625 | specified by prefixing the age argument with a sequence of characters to specify the timestamp types | |
626 | and a colon (<literal>:</literal>): | |
627 | <literal><replaceable>age-by</replaceable>...:<replaceable>cleanup-age</replaceable></literal>. The | |
628 | argument can consist of <constant>a</constant> (<constant>A</constant> for directories), | |
629 | <constant>b</constant> (<constant>B</constant> for directories), <constant>c</constant> | |
630 | (<constant>C</constant> for directories), or <constant>m</constant> (<constant>M</constant> for | |
631 | directories). Those respectively indicate access, creation, last status change, and last modification | |
632 | time of a file system entry. The lower-case letter signifies that the given timestamp type should be | |
633 | considered for files, while the upper-case letter signifies that the given timestamp type should be | |
634 | considered for directories. See <citerefentry | |
635 | project='man-pages'><refentrytitle>statx</refentrytitle><manvolnum>2</manvolnum></citerefentry> file | |
636 | timestamp fields for more details about timestamp types.</para> | |
637 | ||
638 | <para>If not specified, the age-by field defaults to <constant>abcmABM</constant>, i.e. by default all | |
639 | file timestamps are taken into consideration, with the exception of the last status change timestamp | |
640 | (ctime) for directories. This is because the aging logic itself will alter the ctime whenever it | |
641 | deletes a file inside it. To ensure that running the aging logic does not feed back into the next | |
642 | iteration of itself, ctime for directories is ignored by default.</para> | |
7f7a50dd SK |
643 | |
644 | <para>For example:<programlisting> | |
645 | # Files created and modified, and directories accessed more than | |
646 | # an hour ago in "/tmp/foo/bar", are subject to time-based cleanup. | |
647 | d /tmp/foo/bar - - - - bmA:1h -</programlisting></para> | |
aa1f2e52 LP |
648 | |
649 | <para>Note that while the aging algorithm is run a 'shared' BSD file lock (see <citerefentry | |
650 | project='man-pages'><refentrytitle>flock</refentrytitle><manvolnum>2</manvolnum></citerefentry>) is | |
651 | taken on each directory the algorithm descends into (and each directory below that, and so on). If the | |
652 | aging algorithm finds a lock is already taken on some directory, it (and everything below it) is | |
653 | skipped. Applications may use this to temporarily exclude certain directory subtrees from the aging | |
654 | algorithm: the applications can take a BSD file lock themselves, and as long as they keep it aging of | |
655 | the directory and everything below it is disabled.</para> | |
302fbdf2 ZJS |
656 | </refsect2> |
657 | ||
658 | <refsect2> | |
659 | <title>Argument</title> | |
660 | ||
49e87292 LP |
661 | <para>For <varname>L</varname> lines determines the destination path of the symlink. For <varname>c</varname> and |
662 | <varname>b</varname>, determines the major/minor of the device node, with major and minor formatted as integers, | |
663 | separated by <literal>:</literal>, e.g. <literal>1:3</literal>. For <varname>f</varname>, <varname>F</varname>, | |
664 | and <varname>w</varname>, the argument may be used to specify a short string that is written to the file, | |
665 | suffixed by a newline. For <varname>C</varname>, specifies the source file or directory. For <varname>t</varname> | |
666 | and <varname>T</varname>, determines extended attributes to be set. For <varname>a</varname> and | |
667 | <varname>A</varname>, determines ACL attributes to be set. For <varname>h</varname> and <varname>H</varname>, | |
668 | determines the file attributes to set. Ignored for all other lines.</para> | |
2df36d09 ZJS |
669 | |
670 | <para>This field can contain specifiers, see below.</para> | |
302fbdf2 | 671 | </refsect2> |
2df36d09 | 672 | </refsect1> |
302fbdf2 | 673 | |
2df36d09 ZJS |
674 | <refsect1> |
675 | <title>Specifiers</title> | |
676 | ||
677 | <para>Specifiers can be used in the "path" and "argument" fields. | |
751223fe | 678 | An unknown or unresolvable specifier is treated as invalid configuration. |
2df36d09 | 679 | The following expansions are understood:</para> |
0d525a3e | 680 | <table class='specifiers'> |
2df36d09 ZJS |
681 | <title>Specifiers available</title> |
682 | <tgroup cols='3' align='left' colsep='1' rowsep='1'> | |
683 | <colspec colname="spec" /> | |
684 | <colspec colname="mean" /> | |
685 | <colspec colname="detail" /> | |
686 | <thead> | |
687 | <row> | |
688 | <entry>Specifier</entry> | |
689 | <entry>Meaning</entry> | |
690 | <entry>Details</entry> | |
691 | </row> | |
692 | </thead> | |
693 | <tbody> | |
503298b7 | 694 | <xi:include href="standard-specifiers.xml" xpointer="a"/> |
9a515f0a | 695 | <xi:include href="standard-specifiers.xml" xpointer="A"/> |
c83347b4 | 696 | <xi:include href="standard-specifiers.xml" xpointer="b"/> |
503298b7 | 697 | <xi:include href="standard-specifiers.xml" xpointer="B"/> |
709f4c47 LP |
698 | <row> |
699 | <entry><literal>%C</literal></entry> | |
700 | <entry>System or user cache directory</entry> | |
701 | <entry>In <option>--user</option> mode, this is the same as <varname>$XDG_CACHE_HOME</varname>, and <filename>/var/cache</filename> otherwise.</entry> | |
702 | </row> | |
55318801 YW |
703 | <row> |
704 | <entry><literal>%g</literal></entry> | |
705 | <entry>User group</entry> | |
706 | <entry>This is the name of the group running the command. In case of the system instance this resolves to <literal>root</literal>.</entry> | |
707 | </row> | |
708 | <row> | |
709 | <entry><literal>%G</literal></entry> | |
710 | <entry>User GID</entry> | |
711 | <entry>This is the numeric GID of the group running the command. In case of the system instance this resolves to <constant>0</constant>.</entry> | |
712 | </row> | |
709f4c47 LP |
713 | <row> |
714 | <entry><literal>%h</literal></entry> | |
715 | <entry>User home directory</entry> | |
052c59c3 | 716 | <entry>This is the home directory of the user running the command. In case of the system instance this resolves to <literal>/root</literal>.</entry> |
709f4c47 | 717 | </row> |
c83347b4 | 718 | <xi:include href="standard-specifiers.xml" xpointer="H"/> |
e97708fa | 719 | <xi:include href="standard-specifiers.xml" xpointer="l"/> |
2df36d09 | 720 | <row> |
709f4c47 LP |
721 | <entry><literal>%L</literal></entry> |
722 | <entry>System or user log directory</entry> | |
b0343f8c | 723 | <entry>In <option>--user</option> mode, this is the same as <varname>$XDG_CONFIG_HOME</varname> with <filename index="false">/log</filename> appended, and <filename>/var/log</filename> otherwise.</entry> |
ca23eeb5 | 724 | </row> |
c83347b4 | 725 | <xi:include href="standard-specifiers.xml" xpointer="m"/> |
9a515f0a | 726 | <xi:include href="standard-specifiers.xml" xpointer="M"/> |
503298b7 | 727 | <xi:include href="standard-specifiers.xml" xpointer="o"/> |
ca23eeb5 | 728 | <row> |
709f4c47 LP |
729 | <entry><literal>%S</literal></entry> |
730 | <entry>System or user state directory</entry> | |
731 | <entry>In <option>--user</option> mode, this is the same as <varname>$XDG_CONFIG_HOME</varname>, and <filename>/var/lib</filename> otherwise.</entry> | |
ca23eeb5 | 732 | </row> |
5a8575ef ZJS |
733 | <row> |
734 | <entry><literal>%t</literal></entry> | |
735 | <entry>System or user runtime directory</entry> | |
3b121157 | 736 | <entry>In <option>--user</option> mode, this is the same <varname>$XDG_RUNTIME_DIR</varname>, and <filename>/run/</filename> otherwise.</entry> |
5a8575ef | 737 | </row> |
806d919c | 738 | <xi:include href="standard-specifiers.xml" xpointer="T"/> |
5a8575ef | 739 | <row> |
709f4c47 LP |
740 | <entry><literal>%u</literal></entry> |
741 | <entry>User name</entry> | |
052c59c3 | 742 | <entry>This is the name of the user running the command. In case of the system instance this resolves to <literal>root</literal>.</entry> |
5a8575ef ZJS |
743 | </row> |
744 | <row> | |
709f4c47 LP |
745 | <entry><literal>%U</literal></entry> |
746 | <entry>User UID</entry> | |
052c59c3 | 747 | <entry>This is the numeric UID of the user running the command. In case of the system instance this resolves to <constant>0</constant>.</entry> |
5a8575ef | 748 | </row> |
c83347b4 | 749 | <xi:include href="standard-specifiers.xml" xpointer="v"/> |
806d919c | 750 | <xi:include href="standard-specifiers.xml" xpointer="V"/> |
503298b7 LP |
751 | <xi:include href="standard-specifiers.xml" xpointer="w"/> |
752 | <xi:include href="standard-specifiers.xml" xpointer="W"/> | |
c83347b4 | 753 | <xi:include href="standard-specifiers.xml" xpointer="percent"/> |
2df36d09 ZJS |
754 | </tbody> |
755 | </tgroup> | |
756 | </table> | |
302fbdf2 ZJS |
757 | </refsect1> |
758 | ||
759 | <refsect1> | |
4b743d67 | 760 | <title>Examples</title> |
302fbdf2 | 761 | <example> |
4b743d67 ZJS |
762 | <title>Create directories with specific mode and ownership</title> |
763 | <para> | |
0a07667d | 764 | <citerefentry project='die-net'><refentrytitle>screen</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
4b743d67 ZJS |
765 | needs two directories created at boot with specific modes and ownership:</para> |
766 | ||
767 | <programlisting># /usr/lib/tmpfiles.d/screen.conf | |
768 | d /run/screens 1777 root screen 10d | |
769 | d /run/uscreens 0755 root screen 10d12h | |
770 | </programlisting> | |
771 | ||
772 | <para>Contents of <filename>/run/screens</filename> and /run/uscreens will | |
1655cdee | 773 | be cleaned up after 10 and 10½ days, respectively.</para> |
4b743d67 | 774 | </example> |
302fbdf2 | 775 | |
4b743d67 ZJS |
776 | <example> |
777 | <title>Create a directory with a SMACK attribute</title> | |
778 | <programlisting>D /run/cups - - - - | |
779 | t /run/cups - - - - security.SMACK64=printing user.attr-with-spaces="foo bar" | |
780 | </programlisting> | |
781 | ||
b17649ee | 782 | <para>The directory will be owned by root and have default mode. Its contents are |
4b743d67 ZJS |
783 | not subject to time based cleanup, but will be obliterated when |
784 | <command>systemd-tmpfiles --remove</command> runs.</para> | |
302fbdf2 | 785 | </example> |
4b743d67 | 786 | |
302fbdf2 | 787 | <example> |
4b743d67 ZJS |
788 | <title>Create a directory and prevent its contents from cleanup</title> |
789 | <para> | |
0a07667d | 790 | <citerefentry project='die-net'><refentrytitle>abrt</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
4b743d67 ZJS |
791 | needs a directory created at boot with specific mode and ownership and its content |
792 | should be preserved from the automatic cleanup applied to the contents of | |
793 | <filename>/var/tmp</filename>:</para> | |
794 | ||
795 | <programlisting># /usr/lib/tmpfiles.d/tmp.conf | |
796 | d /var/tmp 1777 root root 30d | |
797 | </programlisting> | |
798 | ||
799 | <programlisting># /usr/lib/tmpfiles.d/abrt.conf | |
800 | d /var/tmp/abrt 0755 abrt abrt - | |
df8dee85 ZJS |
801 | </programlisting> |
802 | </example> | |
803 | ||
804 | <example> | |
805 | <title>Apply clean up during boot and based on time</title> | |
806 | ||
807 | <programlisting># /usr/lib/tmpfiles.d/dnf.conf | |
808 | r! /var/cache/dnf/*/*/download_lock.pid | |
809 | r! /var/cache/dnf/*/*/metadata_lock.pid | |
810 | r! /var/lib/dnf/rpmdb_lock.pid | |
e80f1a79 | 811 | e /var/cache/dnf/ - - - 30d |
4b743d67 | 812 | </programlisting> |
302fbdf2 | 813 | |
df8dee85 | 814 | <para>The lock files will be removed during boot. Any files and directories in |
e80f1a79 | 815 | <filename>/var/cache/dnf/</filename> will be removed after they have not been |
df8dee85 | 816 | accessed in 30 days.</para> |
302fbdf2 | 817 | </example> |
ed7fd549 ZJS |
818 | |
819 | <example> | |
b719b26c | 820 | <title>Empty the contents of a cache directory on boot</title> |
ed7fd549 ZJS |
821 | |
822 | <programlisting># /usr/lib/tmpfiles.d/krb5rcache.conf | |
823 | e! /var/cache/krb5rcache - - - 0 | |
824 | </programlisting> | |
825 | ||
826 | <para>Any files and subdirectories in <filename>/var/cache/krb5rcache/</filename> | |
827 | will be removed on boot. The directory will not be created. | |
828 | </para> | |
829 | </example> | |
87d18863 LB |
830 | |
831 | <example> | |
832 | <title>Provision SSH public key access for root user via Credentials in QEMU</title> | |
833 | ||
834 | <programlisting>-smbios type=11,value=io.systemd.credential.binary:tmpfiles.extra=$(echo "f~ /root/.ssh/authorized_keys 700 root root - $(ssh-add -L | base64 -w 0)" | base64 -w 0) | |
835 | </programlisting> | |
836 | ||
837 | <para>By passing this line to QEMU, the public key of the current user will be encoded in | |
838 | base64, added to a tmpfiles.d line that tells systemd-tmpfiles to decode it into | |
839 | <filename>/root/.ssh/authorized_keys</filename>, encode that line itself in base64 and | |
840 | pass it as a Credential that will be picked up by systemd from SMBIOS on boot. | |
841 | </para> | |
842 | </example> | |
302fbdf2 ZJS |
843 | </refsect1> |
844 | ||
6a89d671 ZJS |
845 | <refsect1> |
846 | <title><filename>/run/</filename> and <filename>/var/run/</filename></title> | |
847 | <para><filename>/var/run/</filename> is a deprecated symlink to <filename>/run/</filename>, and | |
848 | applications should use the latter. <command>systemd-tmpfiles</command> will warn if | |
849 | <filename>/var/run/</filename> is used.</para> | |
850 | </refsect1> | |
851 | ||
302fbdf2 ZJS |
852 | <refsect1> |
853 | <title>See Also</title> | |
854 | <para> | |
855 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
856 | <citerefentry><refentrytitle>systemd-tmpfiles</refentrytitle><manvolnum>8</manvolnum></citerefentry>, | |
857 | <citerefentry><refentrytitle>systemd-delta</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
f8eeeaf9 ZJS |
858 | <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>, |
859 | <citerefentry project='man-pages'><refentrytitle>attr</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
860 | <citerefentry project='man-pages'><refentrytitle>getfattr</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
861 | <citerefentry project='man-pages'><refentrytitle>setfattr</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
862 | <citerefentry project='man-pages'><refentrytitle>setfacl</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
fa3f5fd2 | 863 | <citerefentry project='man-pages'><refentrytitle>getfacl</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
5fb13eb5 LP |
864 | <citerefentry project='man-pages'><refentrytitle>chattr</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
865 | <citerefentry project='die-net'><refentrytitle>btrfs-subvolume</refentrytitle><manvolnum>8</manvolnum></citerefentry>, | |
866 | <citerefentry project='die-net'><refentrytitle>btrfs-qgroup</refentrytitle><manvolnum>8</manvolnum></citerefentry> | |
302fbdf2 ZJS |
867 | </para> |
868 | </refsect1> | |
4149f86d BP |
869 | |
870 | </refentry> |