chiark / gitweb /
update TODO
[elogind.git] / man / tmpfiles.d.xml
1 <?xml version="1.0"?>
2 <!--*-nxml-*-->
3 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
4 <!--
5   This file is part of systemd.
6
7   Copyright 2010 Brandon Philips
8
9   systemd is free software; you can redistribute it and/or modify it
10   under the terms of the GNU Lesser General Public License as published by
11   the Free Software Foundation; either version 2.1 of the License, or
12   (at your option) any later version.
13
14   systemd is distributed in the hope that it will be useful, but
15   WITHOUT ANY WARRANTY; without even the implied warranty of
16   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
17   Lesser General Public License for more details.
18
19   You should have received a copy of the GNU Lesser General Public License
20   along with systemd; If not, see <http://www.gnu.org/licenses/>.
21 -->
22 <refentry id="tmpfiles.d">
23
24         <refentryinfo>
25                 <title>tmpfiles.d</title>
26                 <productname>systemd</productname>
27
28                 <authorgroup>
29                         <author>
30                                 <contrib>Documentation</contrib>
31                                 <firstname>Brandon</firstname>
32                                 <surname>Philips</surname>
33                                 <email>brandon@ifup.org</email>
34                         </author>
35                 </authorgroup>
36         </refentryinfo>
37
38         <refmeta>
39                 <refentrytitle>tmpfiles.d</refentrytitle>
40                 <manvolnum>5</manvolnum>
41         </refmeta>
42
43         <refnamediv>
44                 <refname>tmpfiles.d</refname>
45                 <refpurpose>Configuration for creation, deletion and
46                 cleaning of volatile and temporary files</refpurpose>
47         </refnamediv>
48
49         <refsynopsisdiv>
50                 <para><filename>/etc/tmpfiles.d/*.conf</filename></para>
51                 <para><filename>/run/tmpfiles.d/*.conf</filename></para>
52                 <para><filename>/usr/lib/tmpfiles.d/*.conf</filename></para>
53         </refsynopsisdiv>
54
55         <refsect1>
56                 <title>Description</title>
57
58                 <para><command>systemd-tmpfiles</command> uses the
59                 configuration files from the above directories to describe the
60                 creation, cleaning and removal of volatile and
61                 temporary files and directories which usually reside
62                 in directories such as <filename>/run</filename>
63                 or <filename>/tmp</filename>.</para>
64
65                 <para>Volatile and temporary files and directories are
66                 those located in <filename>/run</filename> (and its
67                 alias <filename>/var/run</filename>),
68                 <filename>/tmp</filename>,
69                 <filename>/var/tmp</filename>, the API file systems
70                 such as <filename>/sys</filename> or
71                 <filename>/proc</filename>, as well as some other
72                 directories below <filename>/var</filename>.</para>
73
74                 <para>System daemons frequently require private
75                 runtime directories below <filename>/run</filename> to
76                 place communication sockets and similar in. For these,
77                 consider declaring them in their unit files using
78                 <varname>RuntimeDirectory=</varname>
79                 (see <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details),
80                 if this is feasible.</para>
81         </refsect1>
82
83         <refsect1>
84                 <title>Configuration Format</title>
85
86                 <para>Each configuration file shall be named in the
87                 style of
88                 <filename><replaceable>package</replaceable>.conf</filename>
89                 or
90                 <filename><replaceable>package</replaceable>-<replaceable>part</replaceable>.conf</filename>.
91                 The second variant should be used when it is desirable
92                 to make it easy to override just this part of
93                 configuration.</para>
94
95                 <para>Files in <filename>/etc/tmpfiles.d</filename>
96                 override files with the same name in
97                 <filename>/usr/lib/tmpfiles.d</filename> and
98                 <filename>/run/tmpfiles.d</filename>. Files in
99                 <filename>/run/tmpfiles.d</filename> override files
100                 with the same name in
101                 <filename>/usr/lib/tmpfiles.d</filename>. Packages
102                 should install their configuration files in
103                 <filename>/usr/lib/tmpfiles.d</filename>. Files in
104                 <filename>/etc/tmpfiles.d</filename> are reserved for
105                 the local administrator, who may use this logic to
106                 override the configuration files installed by vendor
107                 packages. All configuration files are sorted by their
108                 filename in lexicographic order, regardless of which
109                 of the directories they reside in. If multiple files
110                 specify the same path, the entry in the file with the
111                 lexicographically earliest name will be applied.
112                 All other conflicting entries will be logged as
113                 errors. When two lines are prefix and suffix of each
114                 other, then the prefix is always processed first, the
115                 suffix later. Otherwise, the files/directories are
116                 processed in the order they are listed.</para>
117
118                 <para>If the administrator wants to disable a
119                 configuration file supplied by the vendor, the
120                 recommended way is to place a symlink to
121                 <filename>/dev/null</filename> in
122                 <filename>/etc/tmpfiles.d/</filename> bearing the
123                 same filename.</para>
124
125                 <para>The configuration format is one line per path
126                 containing type, path, mode, ownership, age, and argument
127                 fields:</para>
128
129                 <programlisting>#Type Path        Mode UID  GID  Age Argument
130 d    /run/user   0755 root root 10d -
131 L    /tmp/foobar -    -    -    -   /dev/null</programlisting>
132
133                 <refsect2>
134                         <title>Type</title>
135
136                         <para>The type consists of a single letter and
137                         optionally an exclamation mark.</para>
138
139                         <para>The following line types are understood:</para>
140
141                         <variablelist>
142                                 <varlistentry>
143                                         <term><varname>f</varname></term>
144                                         <listitem><para>Create a file if it does not exist yet. If the argument parameter is given, it will be written to the file.</para></listitem>
145                                 </varlistentry>
146
147                                 <varlistentry>
148                                         <term><varname>F</varname></term>
149                                         <listitem><para>Create or truncate a file. If the argument parameter is given, it will be written to the file.</para></listitem>
150                                 </varlistentry>
151
152                                 <varlistentry>
153                                         <term><varname>w</varname></term>
154                                         <listitem><para>Write the argument parameter to a file, if the file exists.
155                                             Lines of this type accept shell-style globs in place of normal path
156                                             names. The argument parameter will be written without a trailing
157                                             newline. C-style backslash escapes are interpreted.</para></listitem>
158                                 </varlistentry>
159
160                                 <varlistentry>
161                                         <term><varname>d</varname></term>
162                                         <listitem><para>Create a directory if it does not exist yet.</para></listitem>
163                                 </varlistentry>
164
165                                 <varlistentry>
166                                         <term><varname>D</varname></term>
167                                         <listitem><para>Create or empty a directory.</para></listitem>
168                                 </varlistentry>
169
170                                 <varlistentry>
171                                         <term><varname>p</varname></term>
172                                         <term><varname>p+</varname></term>
173                                         <listitem><para>Create a named
174                                         pipe (FIFO) if it does not
175                                         exist yet. If suffixed with
176                                         <varname>+</varname> and a
177                                         file already exists where the
178                                         pipe is to be created, it will
179                                         be removed and be replaced by
180                                         the pipe.</para></listitem>
181                                 </varlistentry>
182
183                                 <varlistentry>
184                                         <term><varname>L</varname></term>
185                                         <term><varname>L+</varname></term>
186                                         <listitem><para>Create a
187                                         symlink if it does not exist
188                                         yet. If suffixed with
189                                         <varname>+</varname> and a
190                                         file already exists where the
191                                         symlink is to be created, it
192                                         will be removed and be
193                                         replaced by the
194                                         symlink. If the argument is omitted,
195                                         symlinks to files with the same name
196                                         residing in the directory
197                                         <filename>/usr/share/factory/</filename>
198                                         are created.</para></listitem>
199                                 </varlistentry>
200
201                                 <varlistentry>
202                                         <term><varname>c</varname></term>
203                                         <term><varname>c+</varname></term>
204                                         <listitem><para>Create a
205                                         character device node if it
206                                         does not exist yet. If
207                                         suffixed with
208                                         <varname>+</varname> and a
209                                         file already exists where the
210                                         device node is to be created,
211                                         it will be removed and be
212                                         replaced by the device
213                                         node. It is recommended to suffix this
214                                         entry with an exclamation mark to only
215                                         create static device nodes at boot,
216                                         as udev will not manage static device
217                                         nodes that are created at runtime.
218                                         </para></listitem>
219                                 </varlistentry>
220
221                                 <varlistentry>
222                                         <term><varname>b</varname></term>
223                                         <term><varname>b+</varname></term>
224                                         <listitem><para>Create a block
225                                         device node if it does not
226                                         exist yet. If suffixed with
227                                         <varname>+</varname> and a
228                                         file already exists where the
229                                         device node is to be created,
230                                         it will be removed and be
231                                         replaced by the device
232                                         node. It is recommended to suffix this
233                                         entry with an exclamation mark to only
234                                         create static device nodes at boot,
235                                         as udev will not manage static device
236                                         nodes that are created at runtime.
237                                         </para></listitem>
238                                 </varlistentry>
239
240                                 <varlistentry>
241                                         <term><varname>C</varname></term>
242                                         <listitem><para>Recursively
243                                         copy a file or directory, if
244                                         the destination files or
245                                         directories do not exist
246                                         yet. Note that this command
247                                         will not descend into
248                                         subdirectories if the
249                                         destination directory already
250                                         exists. Instead, the entire
251                                         copy operation is
252                                         skipped. If the argument is omitted,
253                                         files from the source directory
254                                         <filename>/usr/share/factory/</filename>
255                                         with the same name are copied.</para></listitem>
256                                 </varlistentry>
257
258                                 <varlistentry>
259                                         <term><varname>x</varname></term>
260                                         <listitem><para>Ignore a path
261                                         during cleaning. Use this type
262                                         to exclude paths from clean-up
263                                         as controlled with the Age
264                                         parameter. Note that lines of
265                                         this type do not influence the
266                                         effect of <varname>r</varname>
267                                         or <varname>R</varname> lines.
268                                         Lines of this type accept
269                                         shell-style globs in place of
270                                         normal path names.
271                                         </para></listitem>
272                                 </varlistentry>
273
274                                 <varlistentry>
275                                         <term><varname>X</varname></term>
276                                         <listitem><para>Ignore a path
277                                         during cleaning. Use this type
278                                         to exclude paths from clean-up
279                                         as controlled with the Age
280                                         parameter. Unlike
281                                         <varname>x</varname>, this
282                                         parameter will not exclude the
283                                         content if path is a
284                                         directory, but only directory
285                                         itself. Note that lines of
286                                         this type do not influence the
287                                         effect of <varname>r</varname>
288                                         or <varname>R</varname> lines.
289                                         Lines of this type accept
290                                         shell-style globs in place of
291                                         normal path names.
292                                         </para></listitem>
293                                 </varlistentry>
294
295                                 <varlistentry>
296                                         <term><varname>r</varname></term>
297                                         <listitem><para>Remove a file
298                                         or directory if it exists.
299                                         This may not be used to remove
300                                         non-empty directories, use
301                                         <varname>R</varname> for that.
302                                         Lines of this type accept
303                                         shell-style globs in place of
304                                         normal path
305                                         names.</para></listitem>
306                                 </varlistentry>
307
308                                 <varlistentry>
309                                         <term><varname>R</varname></term>
310                                         <listitem><para>Recursively
311                                         remove a path and all its
312                                         subdirectories (if it is a
313                                         directory). Lines of this type
314                                         accept shell-style globs in
315                                         place of normal path
316                                         names.</para></listitem>
317                                 </varlistentry>
318
319                                 <varlistentry>
320                                         <term><varname>z</varname></term>
321                                         <listitem><para>Adjust the
322                                         access mode, group and user,
323                                         and restore the SELinux security
324                                         context of a file or directory,
325                                         if it exists. Lines of this
326                                         type accept shell-style globs
327                                         in place of normal path names.
328                                         </para></listitem>
329                                 </varlistentry>
330
331                                 <varlistentry>
332                                         <term><varname>Z</varname></term>
333                                         <listitem><para>Recursively
334                                         set the access mode, group and
335                                         user, and restore the SELinux
336                                         security context of a file or
337                                         directory if it exists, as
338                                         well as of its subdirectories
339                                         and the files contained
340                                         therein (if applicable). Lines
341                                         of this type accept
342                                         shell-style globs in place of
343                                         normal path
344                                         names.</para></listitem>
345                                 </varlistentry>
346                         </variablelist>
347
348                         <para>If the exclamation mark is used, this
349                         line is only safe of execute during boot, and
350                         can break a running system. Lines without the
351                         exclamation mark are presumed to be safe to
352                         execute at any time, e.g. on package upgrades.
353                         <command>systemd-tmpfiles</command> will
354                         execute line with an exclamation mark only if
355                         option <option>--boot</option> is given.
356                         </para>
357
358                         <para>For example:
359                         <programlisting># Make sure these are created by default so that nobody else can
360 d /tmp/.X11-unix 1777 root root 10d
361
362 # Unlink the X11 lock files
363 r! /tmp/.X[0-9]*-lock</programlisting>
364                         The second line in contrast to the first one
365                         would break a running system, and will only be
366                         executed with <option>--boot</option>.</para>
367                 </refsect2>
368
369                 <refsect2>
370                         <title>Path</title>
371
372                         <para>The file system path specification supports simple specifier
373                         expansion. The following expansions are
374                         understood:</para>
375
376                         <table>
377                                 <title>Specifiers available</title>
378                                 <tgroup cols='3' align='left' colsep='1' rowsep='1'>
379                                         <colspec colname="spec" />
380                                         <colspec colname="mean" />
381                                         <colspec colname="detail" />
382                                         <thead>
383                                                 <row>
384                                                         <entry>Specifier</entry>
385                                                         <entry>Meaning</entry>
386                                                         <entry>Details</entry>
387                                                 </row>
388                                         </thead>
389                                         <tbody>
390                                                 <row>
391                                                         <entry><literal>%m</literal></entry>
392                                                         <entry>Machine ID</entry>
393                                                         <entry>The machine ID of the running system, formatted as string. See <citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more information.</entry>
394                                                 </row>
395                                                 <row>
396                                                         <entry><literal>%b</literal></entry>
397                                                         <entry>Boot ID</entry>
398                                                         <entry>The boot ID of the running system, formatted as string. See <citerefentry><refentrytitle>random</refentrytitle><manvolnum>4</manvolnum></citerefentry> for more information.</entry>
399                                                 </row>
400                                                 <row>
401                                                         <entry><literal>%H</literal></entry>
402                                                         <entry>Host name</entry>
403                                                         <entry>The hostname of the running system.</entry>
404                                                 </row>
405                                                 <row>
406                                                         <entry><literal>%v</literal></entry>
407                                                         <entry>Kernel release</entry>
408                                                         <entry>Identical to <command>uname -r</command> output.</entry>
409                                                 </row>
410                                                 <row>
411                                                         <entry><literal>%%</literal></entry>
412                                                         <entry>Escaped %</entry>
413                                                         <entry>Single percent sign.</entry>
414                                                 </row>
415                                         </tbody>
416                                 </tgroup>
417                         </table>
418                 </refsect2>
419
420                 <refsect2>
421                         <title>Mode</title>
422
423                         <para>The file access mode to use when
424                         creating this file or directory. If omitted or
425                         when set to -, the default is used: 0755 for
426                         directories, 0644 for all other file objects.
427                         For <varname>z</varname>, <varname>Z</varname>
428                         lines, if omitted or when set to
429                         <literal>-</literal>, the file access mode
430                         will not be modified. This parameter is
431                         ignored for <varname>x</varname>,
432                         <varname>r</varname>, <varname>R</varname>,
433                         <varname>L</varname> lines.</para>
434
435                         <para>Optionally, if prefixed with
436                         <literal>~</literal>, the access mode is masked
437                         based on the already set access bits for
438                         existing file or directories: if the existing
439                         file has all executable bits unset, all
440                         executable bits are removed from the new
441                         access mode, too. Similarly, if all read bits
442                         are removed from the old access mode, they will
443                         be removed from the new access mode too, and
444                         if all write bits are removed, they will be
445                         removed from the new access mode too. In
446                         addition, the sticky/SUID/SGID bit is removed unless
447                         applied to a directory. This
448                         functionality is particularly useful in
449                         conjunction with <varname>Z</varname>.</para>
450                 </refsect2>
451
452                 <refsect2>
453                         <title>UID, GID</title>
454
455                         <para>The user and group to use for this file
456                         or directory. This may either be a numeric
457                         user/group ID or a user or group name. If
458                         omitted or when set to <literal>-</literal>,
459                         the default 0 (root) is used. For
460                         <varname>z</varname>, <varname>Z</varname>
461                         lines, when omitted or when set to -, the file
462                         ownership will not be modified. These
463                         parameters are ignored for
464                         <varname>x</varname>, <varname>r</varname>,
465                         <varname>R</varname>, <varname>L</varname>
466                         lines.</para>
467                 </refsect2>
468
469                 <refsect2>
470                         <title>Age</title>
471                         <para>The date field, when set, is used to
472                         decide what files to delete when cleaning. If
473                         a file or directory is older than the current
474                         time minus the age field, it is deleted. The
475                         field format is a series of integers each
476                         followed by one of the following
477                         postfixes for the respective time units:</para>
478
479                         <variablelist>
480                                 <varlistentry>
481                                 <term><varname>s</varname></term>
482                                 <term><varname>min</varname></term>
483                                 <term><varname>h</varname></term>
484                                 <term><varname>d</varname></term>
485                                 <term><varname>w</varname></term>
486                                 <term><varname>ms</varname></term>
487                                 <term><varname>m</varname></term>
488                                 <term><varname>us</varname></term></varlistentry>
489                         </variablelist>
490
491                         <para>If multiple integers and units are specified, the time
492                         values are summed up. If an integer is given without a unit,
493                         s is assumed.
494                         </para>
495
496                         <para>When the age is set to zero, the files are cleaned
497                         unconditionally.</para>
498
499                         <para>The age field only applies to lines
500                         starting with <varname>d</varname>,
501                         <varname>D</varname>, and
502                         <varname>x</varname>. If omitted or set to
503                         <literal>-</literal>, no automatic clean-up is
504                         done.</para>
505
506                         <para>If the age field starts with a tilde
507                         character <literal>~</literal>, the clean-up
508                         is only applied to files and directories one
509                         level inside the directory specified, but not
510                         the files and directories immediately inside
511                         it.</para>
512                 </refsect2>
513
514                 <refsect2>
515                         <title>Argument</title>
516
517                         <para>For <varname>L</varname> lines
518                         determines the destination path of the
519                         symlink. For <varname>c</varname>,
520                         <varname>b</varname> determines the
521                         major/minor of the device node, with major and
522                         minor formatted as integers, separated by
523                         <literal>:</literal>, e.g.
524                         <literal>1:3</literal>. For
525                         <varname>f</varname>, <varname>F</varname>,
526                         and <varname>w</varname> may be used to
527                         specify a short string that is written to the
528                         file, suffixed by a newline. For
529                         <varname>C</varname>, specifies the source file
530                         or directory. Ignored for all other
531                         lines.</para>
532                 </refsect2>
533
534         </refsect1>
535
536         <refsect1>
537                 <title>Example</title>
538                 <example>
539                         <title>/etc/tmpfiles.d/screen.conf example</title>
540                         <para><command>screen</command> needs two directories created at boot with specific modes and ownership.</para>
541
542                         <programlisting>d /run/screens  1777 root root 10d
543 d /run/uscreens 0755 root root 10d12h</programlisting>
544                 </example>
545                 <example>
546                         <title>/etc/tmpfiles.d/abrt.conf example</title>
547                         <para><command>abrt</command> needs a directory created at boot with specific mode and ownership and its content should be preserved.</para>
548
549                         <programlisting>d /var/tmp/abrt 0755 abrt abrt
550 x /var/tmp/abrt/*</programlisting>
551                 </example>
552         </refsect1>
553
554         <refsect1>
555                 <title>See Also</title>
556                 <para>
557                         <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
558                         <citerefentry><refentrytitle>systemd-tmpfiles</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
559                         <citerefentry><refentrytitle>systemd-delta</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
560                         <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
561                 </para>
562         </refsect1>
563
564 </refentry>