IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
The second variant should be used when it is desirable to make it
easy to override just this part of configuration.</para>
<para>Files in <filename>/etc/tmpfiles.d</filename> override files
with the same name in <filename>/usr/lib/tmpfiles.d</filename> and
<filename>/run/tmpfiles.d</filename>. Files in
<filename>/run/tmpfiles.d</filename> override files with the same
name in <filename>/usr/lib/tmpfiles.d</filename>. Packages should
install their configuration files in
<filename>/usr/lib/tmpfiles.d</filename>. Files in
<filename>/etc/tmpfiles.d</filename> are reserved for the local
administrator, who may use this logic to override the
configuration files installed by vendor packages. All
configuration files are sorted by their filename in lexicographic
order, regardless of which of the directories they reside in. If
multiple files specify the same path, the entry in the file with
the lexicographically earliest name will be applied. All other
conflicting entries will be logged as errors. When two lines are
prefix and suffix of each other, then the prefix is always
processed first, the suffix later. Otherwise, the
files/directories are processed in the order they are
listed.</para>
<para>If the administrator wants to disable a configuration file
supplied by the vendor, the recommended way is to place a symlink
to <filename>/dev/null</filename> in
<filename>/etc/tmpfiles.d/</filename> bearing the same filename.
</para>
<para>The configuration format is one line per path containing
type, path, mode, ownership, age, and argument fields:</para>
<programlisting>#Type Path Mode UID GID Age Argument
d /run/user 0755 root root 10d -
L /tmp/foobar - - - - /dev/null</programlisting>
<refsect2>
<title>Type</title>
<para>The type consists of a single letter and optionally an
exclamation mark.</para>
<para>The following line types are understood:</para>
<variablelist>
<varlistentry>
<term><varname>f</varname></term>
<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>
</varlistentry>
<varlistentry>
<term><varname>F</varname></term>
<listitem><para>Create or truncate a file. If the argument
parameter is given, it will be written to the file.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>w</varname></term>
<listitem><para>Write the argument parameter to a file, if
the file exists. Lines of this type accept shell-style
globs in place of normal path names. The argument parameter
will be written without a trailing newline. C-style
backslash escapes are interpreted.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>d</varname></term>
<listitem><para>Create a directory if it does not exist yet.
</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>D</varname></term>
<listitem><para>Create or empty a directory.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>v</varname></term>
<listitem><para>Create a subvolume if the path does not
exist yet and the file system supports this
(btrfs). Otherwise create a normal directory, in the same
way as <varname>d</varname>.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>p</varname></term>
<term><varname>p+</varname></term>
<listitem><para>Create a named pipe (FIFO) if it does not
exist yet. If suffixed with <varname>+</varname> and a file
already exists where the pipe is to be created, it will be
removed and be replaced by the pipe.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>L</varname></term>
<term><varname>L+</varname></term>
<listitem><para>Create a symlink if it does not exist
yet. If suffixed with <varname>+</varname> and a file
already exists where the symlink is to be created, it will
be removed and be replaced by the symlink. If the argument
is omitted, symlinks to files with the same name residing in
the directory <filename>/usr/share/factory/</filename> are
created.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>c</varname></term>
<term><varname>c+</varname></term>
<listitem><para>Create a character device node if it does
not exist yet. If suffixed with <varname>+</varname> and a
file already exists where the device node is to be created,
it will be removed and be replaced by the device node. It is
recommended to suffix this entry with an exclamation mark to
only create static device nodes at boot, as udev will not
manage static device nodes that are created at runtime.
</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>b</varname></term>
<term><varname>b+</varname></term>
<listitem><para>Create a block device node if it does not
exist yet. If suffixed with <varname>+</varname> and a file
already exists where the device node is to be created, it
will be removed and be replaced by the device node. It is
recommended to suffix this entry with an exclamation mark to
only create static device nodes at boot, as udev will not
manage static device nodes that are created at runtime.
</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>C</varname></term>
<listitem><para>Recursively copy a file or directory, if the
destination files or directories do not exist yet. Note that
this command will not descend into subdirectories if the
destination directory already exists. Instead, the entire
copy operation is skipped. If the argument is omitted, files
from the source directory
<filename>/usr/share/factory/</filename> with the same name
are copied.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>x</varname></term>
<listitem><para>Ignore a path during cleaning. Use this type
to exclude paths from clean-up as controlled with the Age
parameter. Note that lines of this type do not influence the
effect of <varname>r</varname> or <varname>R</varname>
lines. Lines of this type accept shell-style globs in place
of normal path names. </para></listitem>
</varlistentry>
<varlistentry>
<term><varname>X</varname></term>
<listitem><para>Ignore a path during cleaning. Use this type
to exclude paths from clean-up as controlled with the Age
parameter. Unlike <varname>x</varname>, this parameter will
not exclude the content if path is a directory, but only
directory itself. Note that lines of this type do not
influence the effect of <varname>r</varname> or
<varname>R</varname> lines. Lines of this type accept
shell-style globs in place of normal path names.
</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>r</varname></term>
<listitem><para>Remove a file or directory if it exists.
This may not be used to remove non-empty directories, use
<varname>R</varname> for that. Lines of this type accept
shell-style globs in place of normal path
names.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>R</varname></term>
<listitem><para>Recursively remove a path and all its
subdirectories (if it is a directory). Lines of this type
accept shell-style globs in place of normal path
names.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>z</varname></term>
<listitem><para>Adjust the access mode, group and user, and
restore the SELinux security context of a file or directory,
if it exists. Lines of this type accept shell-style globs in
place of normal path names. </para></listitem>
</varlistentry>
<varlistentry>
<term><varname>Z</varname></term>
<listitem><para>Recursively set the access mode, group and
user, and restore the SELinux security context of a file or
directory if it exists, as well as of its subdirectories and
the files contained therein (if applicable). Lines of this
type accept shell-style globs in place of normal path names.
</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>t</varname></term>
<listitem><para>Set extended attributes on item. It may be
used in conjunction with other types (only
<varname>d</varname>, <varname>D</varname>,
<varname>f</varname>, <varname>F</varname>,
<varname>L</varname>, <varname>p</varname>,
<varname>c</varname>, <varname>b</varname>, makes sense).
If used as a standalone line, then
<command>systemd-tmpfiles</command> will try to set extended
attributes on specified path. This can be especially used
to set SMACK labels. </para></listitem>
</varlistentry>
</variablelist>
<para>If the exclamation mark is used, this line is only safe of
execute during boot, and can break a running system. Lines
without the exclamation mark are presumed to be safe to execute
at any time, e.g. on package upgrades.
<command>systemd-tmpfiles</command> will execute line with an
exclamation mark only if option <option>--boot</option> is
given.</para>
<para>For example:
<programlisting># Make sure these are created by default so that nobody else can
d /tmp/.X11-unix 1777 root root 10d
# Unlink the X11 lock files
r! /tmp/.X[0-9]*-lock</programlisting>
The second line in contrast to the first one would break a
running system, and will only be executed with
<option>--boot</option>.</para>
</refsect2>
<refsect2>
<title>Path</title>
<para>The file system path specification supports simple
specifier expansion. The following expansions are
understood:</para>
<table>
<title>Specifiers available</title>
<tgroupcols='3'align='left'colsep='1'rowsep='1'>
<colspeccolname="spec"/>
<colspeccolname="mean"/>
<colspeccolname="detail"/>
<thead>
<row>
<entry>Specifier</entry>
<entry>Meaning</entry>
<entry>Details</entry>
</row>
</thead>
<tbody>
<row>
<entry><literal>%m</literal></entry>
<entry>Machine ID</entry>
<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>
</row>
<row>
<entry><literal>%b</literal></entry>
<entry>Boot ID</entry>
<entry>The boot ID of the running system, formatted as string. See <citerefentry><refentrytitle>random</refentrytitle><manvolnum>4</manvolnum></citerefentry> for more information.</entry>
</row>
<row>
<entry><literal>%H</literal></entry>
<entry>Host name</entry>
<entry>The hostname of the running system.</entry>
</row>
<row>
<entry><literal>%v</literal></entry>
<entry>Kernel release</entry>
<entry>Identical to <command>uname -r</command> output.</entry>
</row>
<row>
<entry><literal>%%</literal></entry>
<entry>Escaped %</entry>
<entry>Single percent sign.</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect2>
<refsect2>
<title>Mode</title>
<para>The file access mode to use when creating this file or
directory. If omitted or when set to <literal>-</literal>, the
default is used: 0755 for directories, 0644 for all other file
objects. For <varname>z</varname>, <varname>Z</varname> lines,
if omitted or when set to <literal>-</literal>, the file access
mode will not be modified. This parameter is ignored for