1UDEVADM(8) udevadm UDEVADM(8)
2
3
4
6 udevadm - udev management tool
7
9 udevadm [--debug] [--version] [--help]
10
11 udevadm info options
12
13 udevadm trigger [options]
14
15 udevadm settle [options]
16
17 udevadm control command
18
19 udevadm monitor [options]
20
21 udevadm test [options] devpath
22
24 udevadm expects a command and command specific options. It controls the
25 runtime behavior of udev, requests kernel events, manages the event
26 queue, and provides simple debugging mechanisms.
27
29 --debug
30 Print debug messages to stderr.
31
32 --version
33 Print version number.
34
35 --help
36 Print help text.
37
38 udevadm info options
39 Queries the udev database for device information stored in the udev
40 database. It can also query the properties of a device from its sysfs
41 representation to help creating udev rules that match this device.
42
43 --query=type
44 Query the database for specified type of device data. It needs the
45 --path or --name to identify the specified device. Valid queries
46 are: name, symlink, path, property, all.
47
48 --path=devpath
49 The devpath of the device to query.
50
51 --name=file
52 The name of the device node or a symlink to query
53
54 --root
55 The udev root directory: /dev. If used in conjunction with a name
56 or symlink query, the query returns the absolute path including the
57 root directory.
58
59 --attribute-walk
60 Print all sysfs properties of the specified device that can be used
61 in udev rules to match the specified device. It prints all devices
62 along the chain, up to the root of sysfs that can be used in udev
63 rules.
64
65 --device-id-of-file=file
66 Print major/minor numbers of the underlying device, where the file
67 lives on.
68
69 --export-db
70 Export the content of the udev database.
71
72 --version
73 Print version.
74
75 --help
76 Print help text.
77
78 udevadm trigger [options]
79 Request device events from the kernel. Primarily used to replay events
80 at system coldplug time.
81
82 --verbose
83 Print the list of devices which will be triggered.
84
85 --dry-run
86 Do not actually trigger the event.
87
88 --type=type
89 Trigger a specific type of devices. Valid types are: devices,
90 subsystems, failed. The default value is devices.
91
92 --action=action
93 Type of event to be triggered. The default value is change.
94
95 --subsystem-match=subsystem
96 Trigger events for devices which belong to a matching subsystem.
97 This option can be specified multiple times and supports shell
98 style pattern matching.
99
100 --subsystem-nomatch=subsystem
101 Do not trigger events for devices which belong to a matching
102 subsystem. This option can be specified multiple times and supports
103 shell style pattern matching.
104
105 --attr-match=attribute=value
106 Trigger events for devices with a matching sysfs attribute. If a
107 value is specified along with the attribute name, the content of
108 the attribute is matched against the given value using shell style
109 pattern matching. If no value is specified, the existence of the
110 sysfs attribute is checked. This option can be specified multiple
111 times.
112
113 --attr-nomatch=attribute=value
114 Do not trigger events for devices with a matching sysfs attribute.
115 If a value is specified along with the attribute name, the content
116 of the attribute is matched against the given value using shell
117 style pattern matching. If no value is specified, the existence of
118 the sysfs attribute is checked. This option can be specified
119 multiple times.
120
121 --property-match=property=value
122 Trigger events for devices with a matching property value. This
123 option can be specified multiple times and supports shell style
124 pattern matching.
125
126 --tag-match=property
127 Trigger events for devices with a matching tag. This option can be
128 specified multiple times.
129
130 --sysname-match=name
131 Trigger events for devices with a matching sys device name. This
132 option can be specified multiple times and supports shell style
133 pattern matching.
134
135 udevadm settle [options]
136 Watches the udev event queue, and exits if all current events are
137 handled.
138
139 --timeout=seconds
140 Maximum number of seconds to wait for the event queue to become
141 empty. The default value is 180 seconds. A value of 0 will check if
142 the queue is empty and always return immediately.
143
144 --seq-start=seqnum
145 Wait only for events after the given sequence number.
146
147 --seq-end=seqnum
148 Wait only for events before the given sequence number.
149
150 --exit-if-exists=file
151 Stop waiting if file exists.
152
153 --quiet
154 Do not print any output, like the remaining queue entries when
155 reaching the timeout.
156
157 --help
158 Print help text.
159
160 udevadm control command
161 Modify the internal state of the running udev daemon.
162
163 --log-priority=value
164 Set the internal log level of udevd. Valid values are the numerical
165 syslog priorities or their textual representations: err, info and
166 debug.
167
168 --stop-exec-queue
169 Signal udevd to stop executing new events. Incoming events will be
170 queued.
171
172 --start-exec-queue
173 Signal udevd to enable the execution of events.
174
175 --reload-rules
176 Signal udevd to reload the rules files. The udev daemon detects
177 changes automatically, this option is usually not needed. Reloading
178 rules does not apply any changes to already existing devices.
179
180 --property=KEY=value
181 Set a global property for all events.
182
183 --children-max=value
184 Set the maximum number of events, udevd will handle at the same
185 time.
186
187 --help
188 Print help text.
189
190 udevadm monitor [options]
191 Listens to the kernel uevents and events sent out by a udev rule and
192 prints the devpath of the event to the console. It can be used to
193 analyze the event timing, by comparing the timestamps of the kernel
194 uevent and the udev event.
195
196 --kernel
197 Print the kernel uevents.
198
199 --udev
200 Print the udev event after the rule processing.
201
202 --property
203 Also print the properties of the event.
204
205 --subsystem-match=string[/string]
206 Filter events by subsystem[/devtype]. Only udev events with a
207 matching subsystem value will pass.
208
209 --tag-match=string
210 Filter events by property. Only udev events with a given tag
211 attached will pass.
212
213 --help
214 Print help text.
215
216 udevadm test [options] devpath
217 Simulate a udev event run for the given device, and print debug output.
218
219 --action=string
220 The action string.
221
222 --subsystem=string
223 The subsystem string.
224
225 --help
226 Print help text.
227
229 Written by Kay Sievers kay.sievers@vrfy.org.
230
232 udev(7) udevd(8)
233
234
235
236udev 08/11/2010 UDEVADM(8)