X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.device.xml;h=557f15f906d79615e698ad521c1c2274406da719;hp=96ebe890953fd3c499ab4b8120c2c86089de4496;hb=67826132adfdf626413f08fb664debd4a7ec35b7;hpb=79640424059328268b9fb6c5fa8eb777b27a177e;ds=sidebyside diff --git a/man/systemd.device.xml b/man/systemd.device.xml index 96ebe8909..557f15f90 100644 --- a/man/systemd.device.xml +++ b/man/systemd.device.xml @@ -70,12 +70,15 @@ 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. + 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 @@ -93,24 +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, when a specific device becomes - available. Note that this and the + 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. + + 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 systemd - unit. + 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. + @@ -129,16 +149,22 @@ even if it shows up in the udev tree. If this property is unset or set to 1, the device will be considered - plugged the moment it shows up in the + plugged if it is 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 + 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. + 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. @@ -159,7 +185,7 @@ See Also systemd1, - systemctl8, + systemctl1, systemd.unit5, udev7, systemd.directives7