- <refsect1><title>OPTIONS</title>
-
- <refsect2><title>udevadm info <replaceable>options</replaceable></title>
- <para>Queries the udev database for device information
- stored in the udev database. It can also query the properties
- of a device from its sysfs representation to help creating udev
- rules that match this device.</para>
- <variablelist>
- <varlistentry>
- <term><option>--query=<replaceable>type</replaceable></option></term>
- <listitem>
- <para>Query the database for specified type of device data. It needs the
- <option>--path</option> or <option>--name</option> to identify the specified
- device. Valid queries are:
- <command>name</command>, <command>symlink</command>, <command>path</command>,
- <command>env</command>, <command>all</command>.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--path=<replaceable>devpath</replaceable></option></term>
- <listitem>
- <para>The devpath of the device to query.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--name=<replaceable>file</replaceable></option></term>
- <listitem>
- <para>The name of the device node or a symlink to query</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--root</option></term>
- <listitem>
- <para>The udev root directory: <filename>/dev</filename>. If used in conjunction
- with a <command>name</command> or <command>symlink</command> query, the
- query returns the absolute path including the root directory.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--attribute-walk</option></term>
- <listitem>
- <para>Print all sysfs properties of the specified device that can be used
- in udev rules to match the specified device. It prints all devices
- along the chain, up to the root of sysfs that can be used in udev rules.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--device-id-of-file=<replaceable>file</replaceable></option></term>
- <listitem>
- <para>Print major/minor numbers of the underlying device, where the file
- lives on.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--export-db</option></term>
- <listitem>
- <para>Export the content of the udev database.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--version</option></term>
- <listitem>
- <para>Print version.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--help</option></term>
- <listitem>
- <para>Print help text.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- </refsect2>
-
- <refsect2><title>udevadm trigger <optional>options</optional></title>
- <para>Request device uevents, usually used to replay events at system coldplug.</para>
- <variablelist>
- <varlistentry>
- <term><option>--verbose</option></term>
- <listitem>
- <para>Print the list of devices which will be triggered.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--dry-run</option></term>
- <listitem>
- <para>Do not actually trigger the event.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--retry-failed</option></term>
- <listitem>
- <para>Trigger only the events which are failed during a previous run.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--action=<replaceable>action</replaceable></option></term>
- <listitem>
- <para>Type of event to be triggered. The default value is "add".</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--subsystem-match=<replaceable>subsystem</replaceable></option></term>
- <listitem>
- <para>Trigger events for devices which belong to a matching subsystem. This option
- can be specified multiple times and supports shell style pattern matching.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--subsystem-nomatch=<replaceable>subsystem</replaceable></option></term>
- <listitem>
- <para>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.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--attr-match=<replaceable>attribute</replaceable>=<replaceable>value</replaceable></option></term>
- <listitem>
- <para>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.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--attr-nomatch=<replaceable>attribute</replaceable>=<replaceable>value</replaceable></option></term>
- <listitem>
- <para>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.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--socket=<replaceable>path</replaceable></option></term>
- <listitem>
- <para>Pass the synthesized events to the specified socket, instead of triggering
- a global kernel event. All available event values will be send in the same format
- the kernel sends an uevent, or <option>RUN+="socket:<replaceable>path</replaceable>"</option>
- sends a message. If the first character of the specified path is an @ character,
- an abstract namespace socket is used, instead of an existing socket file.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--env=<replaceable>KEY</replaceable>=<replaceable>value</replaceable></option></term>
- <listitem>
- <para>Pass an additional environemt key to the event. This works only with the
- --socket option.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- </refsect2>