X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.device.xml;h=1bbd32248fce34226dd9359068ff2190d0d7d10b;hb=12179984a38fe74581333fbcdc11c822d81f505f;hp=a5395a1d489f80cbe2672d420e1794602eca9ee5;hpb=b439c6ee04967fa988d232e0765f972cb27b1877;p=elogind.git
diff --git a/man/systemd.device.xml b/man/systemd.device.xml
index a5395a1d4..1bbd32248 100644
--- a/man/systemd.device.xml
+++ b/man/systemd.device.xml
@@ -9,16 +9,16 @@
Copyright 2010 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
- under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
+ under the terms of the GNU Lesser General Public License as published by
+ the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- General Public License for more details.
+ Lesser General Public License for more details.
- You should have received a copy of the GNU General Public License
+ You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see .
-->
@@ -44,18 +44,18 @@
systemd.device
- systemd device configuration files
+ Device unit configuration
- systemd.device
+ device.device
Description
A unit configuration file whose name ends in
- .device encodes information about
+ .device encodes information about
a device unit as exposed in the
sysfs/udev7
device tree.
@@ -64,21 +64,26 @@
systemd.unit5
for the common options of all unit configuration
files. The common configuration items are configured
- in the generic [Unit] and [Install] sections. A
- separate [Device] section does not exist, since no
- device-specific options may be configured.
-
- systemd will automatically create dynamic device
- units for all kernel devices that are marked with the
- "systemd" udev tag (by default all block and network
- devices, and a few others). This may be used to define
- dependencies between devices and other
- units.
+ in the generic [Unit] and
+ [Install] sections. A separate
+ [Device] section does not exist,
+ since no device-specific options may be
+ configured.
+
+ systemd will dynamically create device units for
+ all kernel devices that are marked with the "systemd"
+ udev tag (by default all block and network devices,
+ and a few others). This may be used to define
+ dependencies between devices and other units. To tag a
+ udev device use TAG+="systemd" in
+ the udev rules file, see
+ udev7
+ for details.
Device units are named after the
/sys and
/dev paths they control. Example:
- the device /dev/sda5 is exposed
+ the device /dev/sda5 is exposed
in systemd as dev-sda5.device. For
details about the escaping logic used to convert a
file system path to a unit name see
@@ -91,18 +96,41 @@
The settings of device units may either be
configured via unit files, or directly from the udev
- database (which is recommended). The following udev
+ database (which is recommended). The following udev device
properties are understood by systemd:
-
+
SYSTEMD_WANTS=
+ SYSTEMD_USER_WANTS=
Adds dependencies of
- type Wants from
- this unit to all listed units. This
- may be used to activate arbitrary units,
+ type Wants from the
+ device unit to all listed units. The
+ first form is used by the system
+ systemd instance, the second by user
+ systemd instances. Those settings may
+ be used to activate arbitrary units
when a specific device becomes
- available.
+ available.
+
+ Note that this and the
+ other tags are not taken into account
+ unless the device is tagged with the
+ systemd string in
+ the udev database, because otherwise
+ the device is not exposed as a systemd
+ unit (see above).
+
+ Note that systemd will only act
+ on Wants
+ dependencies when a device first
+ becomes active. It will not act on
+ them if they are added to devices that
+ are already active. Use
+ SYSTEMD_READY= (see
+ below) to influence on which udev
+ event to trigger the dependencies.
+
@@ -114,6 +142,31 @@
name. (See above.)
+
+ SYSTEMD_READY=
+ If set to 0, systemd
+ will consider this device unplugged
+ even if it shows up in the udev
+ tree. If this property is unset or set
+ to 1, the device will be considered
+ plugged if it visible in the
+ udev tree. This property has no
+ 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
+ uninitialized state in the tree, and
+ for which a changed
+ event is generated the moment they are
+ fully set up. Note that
+ SYSTEMD_WANTS= (see
+ above) is not acted on as long as
+ SYSTEMD_READY=0 is
+ set for a device.
+
+
ID_MODEL_FROM_DATABASE=
ID_MODEL=
@@ -131,10 +184,11 @@
See Also
- systemd8,
+ systemd1,
systemctl8,
systemd.unit5,
- udev7
+ udev7,
+ systemd.directives7