X-Git-Url: http://git.ipfire.org/?a=blobdiff_plain;f=man%2Fudevadm.xml;h=a716b1819d783cdc8a67e788c89c23d20523b288;hb=6b222c4b0227f9914446ac54754aea867f742be4;hp=44be7b3f894b5117dc5f5bdf152e2e1d16ab72c7;hpb=3c79311a6a4518acf68215f72c3e8c78f220e710;p=thirdparty%2Fsystemd.git diff --git a/man/udevadm.xml b/man/udevadm.xml index 44be7b3f894..a716b1819d7 100644 --- a/man/udevadm.xml +++ b/man/udevadm.xml @@ -1,10 +1,7 @@ - - - + @@ -143,22 +140,25 @@ - Print output as key/value pairs. Values are enclosed in single quotes. + Print output as key/value pairs. Values are enclosed in single quotes. + This takes effects only when or + is specified. - Add a prefix to the key name of exported values. + Add a prefix to the key name of exported values. + This implies . - Print major/minor numbers of the underlying device, where the file - lives on. + Print major/minor numbers of the underlying device, where the file lives on. + If this is specified, all positional arguments are ignored. @@ -175,6 +175,14 @@ Cleanup the udev database. + + + + + Wait for device to be initialized. If argument SECONDS + is not specified, the default is to wait forever. + + @@ -182,11 +190,11 @@ udevadm trigger <arg choice="opt"><replaceable>options</replaceable></arg> - <arg choice="opt" rep="repeat"><replaceable>devpath</replaceable>|<replaceable>file</replaceable>|<replaceable>unit</replaceable></arg> + <arg choice="opt"><replaceable>devpath</replaceable>|<replaceable>file</replaceable>|<replaceable>unit</replaceable></arg> Request device events from the kernel. Primarily used to replay events at system coldplug time. - Takes one or more device specifications as arguments. See the description of info + Takes device specifications as positional arguments. See the description of info above. @@ -217,8 +225,12 @@ - Type of event to be triggered. The default value is - change. + Type of event to be triggered. Possible actions are add, + remove, change, move, + online, offline, bind, + and unbind. Also, the special value help can be used + to list the possible actions. The default value is change. + @@ -226,8 +238,9 @@ Trigger events for devices which belong to a - matching subsystem. This option can be specified multiple - times and supports shell style pattern matching. + matching subsystem. This option supports shell style pattern matching. + When this option is specified more than once, then each matching result is ORed, that is, + all the devices in each subsystem are triggered. @@ -235,77 +248,74 @@ Do not trigger events for devices which belong to a matching subsystem. This option - can be specified multiple times and supports shell style pattern matching. + supports shell style pattern matching. When this option is specified more than once, + then each matching result is ANDed, that is, devices which do not match all specified + subsystems are triggered. - Trigger events for devices with a matching sysfs - attribute. If a value is specified along with the - attribute name, the content of the attribute is matched - against the given value using shell style pattern - matching. If no value is specified, the existence of the - sysfs attribute is checked. This option can be specified - multiple times. + Trigger events for devices with a matching sysfs attribute. If a value is specified along + with the attribute name, the content of the attribute is matched against the given value using + shell style pattern matching. If no value is specified, the existence of the sysfs attribute is + checked. When this option is specified multiple times, then each matching result is ANDed, + that is, only devices which have all specified attributes are triggered. - Do not trigger events for devices with a matching - sysfs attribute. If a value is specified along with the - attribute name, the content of the attribute is matched - against the given value using shell style pattern - matching. If no value is specified, the existence of the - sysfs attribute is checked. This option can be specified - multiple times. + Do not trigger events for devices with a matching sysfs attribute. If a value is specified + along with the attribute name, the content of the attribute is matched against the given value + using shell style pattern matching. If no value is specified, the existence of the sysfs attribute + is checked. When this option is specified multiple times, then each matching result is ANDed, + that is, only devices which have none of the specified attributes are triggered. - Trigger events for devices with a matching property - value. This option can be specified multiple times and - supports shell style pattern matching. + Trigger events for devices with a matching property value. This option supports shell style + pattern matching. When this option is specified more than once, then each matching result is ORed, + that is, devices which have one of the specified properties are triggered. - Trigger events for devices with a matching tag. This - option can be specified multiple times. + Trigger events for devices with a matching tag. When this option is specified multiple times, + then each matching result is ANDed, that is, devices which have all specified tags are triggered. - + - Trigger events for devices for which the last component - (i.e. the filename) of the /sys path matches - the specified PATH. This option can be - specified multiple times and also supports shell style pattern - matching. + Trigger events for devices for which the last component (i.e. the filename) of the + /sys path matches the specified PATH. This option + supports shell style pattern matching. When this option is specified more than once, then each + matching result is ORed, that is, all devices which have any of the specified + NAME are triggered. - Trigger events for devices with a matching - device path. This option can be specified multiple - times. + Trigger events for devices with a matching device path. When this option is specified more than once, + then each matching result is ORed, that is, all specified devices are triggered. - Trigger events for all children of a given - device. + Trigger events for all children of a given device. When this option is specified more than once, + then each matching result is ORed, that is, all children of each specified device are triggered. @@ -319,6 +329,14 @@ the same command to finish. + + + + Before triggering uevents, wait for systemd-udevd daemon to be initialized. + Optionally takes timeout value. Default timeout is 5 seconds. This is equivalent to invoke + invoking udevadm control --ping before udevadm trigger. + + @@ -341,7 +359,9 @@ Maximum number of seconds to wait for the event queue to become empty. The default value is 120 seconds. A value of 0 will check if the queue is empty and always - return immediately. + return immediately. A non-zero value will return an exit + code of 0 if queue became empty before timeout was reached, + non-zero otherwise. @@ -354,6 +374,10 @@ + + See + systemd-udev-settle.service8 + for more information. udevadm control <replaceable>option</replaceable> @@ -363,7 +387,13 @@ - Signal and wait for systemd-udevd to exit. + Signal and wait for systemd-udevd to exit. No option except for + can be specified after this option. + Note that systemd-udevd.service contains + and so as a result, this option restarts systemd-udevd. + If you want to stop systemd-udevd.service, please use the following: + systemctl stop systemd-udevd-control.socket systemd-udevd-kernel.socket systemd-udevd.service + @@ -419,6 +449,13 @@ same time. + + + + Send a ping message to systemd-udevd and wait for the reply. This may be useful to check that + systemd-udevd daemon is running. + + seconds @@ -464,14 +501,18 @@ - Filter kernel uevents and udev events by subsystem[/devtype]. Only events with a matching subsystem value will pass. + Filter kernel uevents and udev events by subsystem[/devtype]. Only events with a matching subsystem value will pass. + When this option is specified more than once, then each matching result is ORed, that is, all devices in the specified + subsystems are monitored. - Filter udev events by tag. Only udev events with a given tag attached will pass. + Filter udev events by tag. Only udev events with a given tag attached will pass. + When this option is specified more than once, then each matching result is ORed, that is, devices which have one of the + specified tags are monitored. @@ -487,9 +528,13 @@ - + - The action string. + Type of event to be simulated. Possible actions are add, + remove, change, move, + online, offline, bind, + and unbind. Also, the special value help can be used + to list the possible actions. The default value is add.