<refnamediv>
<refname>systemd.device</refname>
- <refpurpose>systemd device configuration files</refpurpose>
+ <refpurpose>Device unit configuration</refpurpose>
</refnamediv>
<refsynopsisdiv>
- <para><filename>systemd.device</filename></para>
+ <para><filename><replaceable>device</replaceable>.device</filename></para>
</refsynopsisdiv>
<refsect1>
<para>Device units are named after the
<filename>/sys</filename> and
<filename>/dev</filename> paths they control. Example:
- the device <filename>/dev/sda5</filename> is exposed
+ the device <filename noindex='true'>/dev/sda5</filename> is exposed
in systemd as <filename>dev-sda5.device</filename>. For
details about the escaping logic used to convert a
file system path to a unit name see
database (which is recommended). The following udev
properties are understood by systemd:</para>
- <variablelist>
+ <variablelist class='udev-directives'>
<varlistentry>
<term><varname>SYSTEMD_WANTS=</varname></term>
<listitem><para>Adds dependencies of
to 1 the device will be considered
plugged the moment it shows up in the
udev tree. This property has no
- influence on the behaviour when a
+ influence on the behavior when a
device disappears from the udev
tree. This option is useful to support
devices that initially show up in an
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
- <citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry>
+ <citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
+ <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>
</para>
</refsect1>