X-Git-Url: http://git.ipfire.org/?a=blobdiff_plain;f=man%2Fsystemd.device.xml;h=9e53a46a0660eaa2e978db00f4821fc429bcaf11;hb=eea10b26f78806d7b244af7d37f75fd567c69610;hp=085fd62bceef8d2428d48d7b818df4ec375e2d6e;hpb=2e2f6a01a008156ed457040c4757fa541be4a055;p=thirdparty%2Fsystemd.git diff --git a/man/systemd.device.xml b/man/systemd.device.xml index 085fd62bcee..9e53a46a066 100644 --- a/man/systemd.device.xml +++ b/man/systemd.device.xml @@ -1,7 +1,7 @@ - + "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> + @@ -26,11 +26,10 @@ Description - A unit configuration file whose name ends in - .device encodes information about a device unit - as exposed in the - sysfs/udev7 - device tree. + A unit configuration file whose name ends in .device encodes information about a + device unit as exposed in the + sysfs/udev7 device + tree. This may be used to define dependencies between devices and other units. This unit type has no specific options. See systemd.unit5 @@ -40,23 +39,23 @@ 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 + 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). Note + that if systemd-udevd.service is not running, no device units will be + available (for example in a typical container). + + Device units are named after the /sys/ + and /dev/ paths they control. Example: 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 systemd.unit5. + To tag a udev device, use TAG+="systemd" in the udev rules file, see + udev7 for details. + + Device units will be reloaded by systemd whenever the corresponding device generates a changed event. Other units can use ReloadPropagatedFrom= to react @@ -148,18 +147,25 @@ + + + + Options + Device unit files may include [Unit] and [Install] sections, which are described in + systemd.unit5. No + options specific to this file type are supported. See Also - - systemd1, - systemctl1, - systemd.unit5, - udev7, - systemd.directives7 - + + systemd1 + systemctl1 + systemd.unit5 + udev7 + systemd.directives7 +