udevadmeudevDeveloperKaySieverskay@vrfy.orgudevadm8udevadmudev management tooludevadmudevadm info optionsudevadm trigger optionsudevadm settle optionsudevadm control commandudevadm monitor optionsudevadm hwdb optionsudevadm test optionsdevpathudevadm test-builtin optionscommanddevpathDescriptionudevadm expects a command and command
specific options. It controls the runtime behavior of
udev, requests kernel events, manages
the event queue, and provides simple debugging mechanisms.OptionsPrint debug messages to standard error.Print version number.Print help text.udevadm info
optionsdevpath|fileQueries 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.Query the database for the specified type of device
data. It needs the or
to identify the specified device.
Valid TYPEs are:
name, symlink,
path, property,
all.The /sys path of the device to
query, e.g.
/sys/class/block/sda.
Note that this option usually is not very useful, since
udev can guess the type of the
argument, so udevadm
--devpath=/class/block/sda is equivalent to
udevadm /sys/class/block/sda.The name of the device node or a symlink to query,
e.g. /dev/sda.
Note that this option usually is not very useful, since
udev can guess the type of the
argument, so udevadm --name=sda is
equivalent to udevadm /dev/sda.Print absolute paths in name or symlink
query.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.Print output as key/value pairs. Values are enclosed in single quotes.Add a prefix to the key name of exported values.Print major/minor numbers of the underlying device, where the file
lives on.Export the content of the udev database.Cleanup the udev database.Print version.Print help text.In addition an optional positional argument can be used
to specify a device name or a sys path. It must start with
/dev or /sys
respectively.udevadm trigger
optionsdevpath|fileRequest device events from the kernel. Primarily used to replay events at system coldplug time.Print the list of devices which will be triggered.Do not actually trigger the event.Trigger a specific type of devices. Valid types are:
devices, subsystems.
The default value is devices.Type of event to be triggered. The default value is
change.Trigger events for devices which belong to a
matching subsystem. This option can be specified multiple
times and supports shell style pattern matching.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.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. This option can be specified
multiple times.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 tag. This
option can be specified multiple times.Trigger events for devices with a matching sys
device path. This option can be specified multiple times
and supports shell style pattern matching.Trigger events for devices with a matching
device path. This options can be specified multiple
times.Trigger events for all children of a given
device.Print help text.In addition optional positional arguments can be used
to specify device names or sys paths. They must start with
/dev or /sys
respectively.udevadm settle
optionsWatches the udev event queue, and exits if all current events are handled.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.Stop waiting if file exists.Print help text.udevadm control commandModify the internal state of the running udev daemon.Signal and wait for udevd to exit.Set the internal log level of
udevd. Valid values are the
numerical syslog priorities or their textual
representations: ,
, ,
, ,
, , and
.Signal udevd to stop executing new events. Incoming events
will be queued.Signal udevd to enable the execution of events.Signal udevd to reload the rules files and other databases like the kernel
module index. Reloading rules and databases does not apply any changes to already
existing devices; the new configuration will only be applied to new events.Set a global property for all events.valueSet the maximum number of events, udevd will handle at the
same time.secondsThe maximum number of seconds to wait for a reply from udevd.Print help text.udevadm monitor
optionsListens to the kernel uevents and events sent out by a udev rule
and prints the devpath of the event to the console. It can be used to analyze the
event timing, by comparing the timestamps of the kernel uevent and the udev event.
Print the kernel uevents.Print the udev event after the rule processing.Also print the properties of the event.Filter events by subsystem[/devtype]. Only udev events with a matching subsystem value will pass.Filter events by property. Only udev events with a given tag attached will pass.Print help text.udevadm hwdb
optionsMaintain the hardware database index in /etc/udev/hwdb.bin.Compile the hardware database information located in /usr/lib/udev/hwdb.d/,
/etc/udev/hwdb.d/ and store it in /etc/udev/hwdb.bin. This should be done after
any update to the source files; it will not be called automatically. The running
udev daemon will detect a new database on its own and does not need to be
notified about it.Query the database with a modalias string, and print the
retrieved properties.Alternative root path in the file system for reading and writing files.Print help text.udevadm test
optionsdevpathSimulate a udev event run for the given device, and print debug output.The action string.Specify when udevadm should resolve names of users
and groups. When set to early (the
default), names will be resolved when the rules are
parsed. When set to late, names will
be resolved for every event. When set to
never, names will never be resolved
and all devices will be owned by root.Print help text.udevadm test-builtin
optionscommanddevpathRun a built-in command COMMAND
for device DEVPATH, and print debug
output.Print help text.See Alsoudev7,
udevd.service8