{ "content": [ { "type": "text", "text": "# UDEVADM (man)\n\n## NAME\n\nudevadm - udev management tool\n\n## SYNOPSIS\n\nudevadm [--debug] [--version] [--help]\n\n## DESCRIPTION\n\nudevadm expects a command and command specific options. It controls the runtime behavior of\nsystemd-udevd, requests kernel events, manages the event queue, and provides simple debugging\nmechanisms.\n\n## TLDR\n\n> Linux `udev` management tool.\n\n- Monitor all device events:\n `sudo udevadm monitor`\n- Print `uevents` sent out by the kernel:\n `sudo udevadm monitor {{-k|--kernel}}`\n- Print device events after being processed by `udev`:\n `sudo udevadm monitor {{-u|--udev}}`\n- List attributes of device `/dev/sda`:\n `sudo udevadm info {{-a|--attribute-walk}} /dev/sda`\n- Reload all `udev` rules:\n `sudo udevadm control {{-R|--reload}}`\n- Trigger all `udev` rules to run:\n `sudo udevadm trigger`\n- Test an event run by simulating loading of `/dev/sda`:\n `sudo udevadm test /dev/sda`\n\n*Source: tldr-pages*\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS** (4 subsections)\n- **DESCRIPTION**\n- **OPTIONS** (54 subsections)\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "UDEVADM", "section": "", "mode": "man", "summary": "udevadm - udev management tool", "synopsis": "udevadm [--debug] [--version] [--help]", "tldr_summary": "Linux `udev` management tool.", "tldr_examples": [ { "description": "Monitor all device events", "command": "sudo udevadm monitor" }, { "description": "Print `uevents` sent out by the kernel", "command": "sudo udevadm monitor {{-k|--kernel}}" }, { "description": "Print device events after being processed by `udev`", "command": "sudo udevadm monitor {{-u|--udev}}" }, { "description": "List attributes of device `/dev/sda`", "command": "sudo udevadm info {{-a|--attribute-walk}} /dev/sda" }, { "description": "Reload all `udev` rules", "command": "sudo udevadm control {{-R|--reload}}" }, { "description": "Trigger all `udev` rules to run", "command": "sudo udevadm trigger" }, { "description": "Test an event run by simulating loading of `/dev/sda`", "command": "sudo udevadm test /dev/sda" } ], "tldr_source": "official", "flags": [ { "flag": "-d", "long": "--debug", "arg": null, "description": "Print debug messages to standard error. This option is implied in udevadm test and udevadm test-builtin commands." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Print a short help text and exit. udevadm info [options] [devpath|file|unit...] Query the udev database for device information. Positional arguments should be used to specify one or more devices. Each one may be a device name (in which case it must start with /dev/), a sys path (in which case it must start with /sys/), or a systemd device unit name (in which case it must end with \".device\", see systemd.device(5))." }, { "flag": "-q", "long": null, "arg": null, "description": "Query the database for the specified type of device data. Valid TYPEs are: name, symlink, path, property, all." }, { "flag": "-p", "long": null, "arg": null, "description": "The /sys/ path of the device to query, e.g. [/sys/]/class/block/sda. This option is an alternative to the positional argument with a /sys/ prefix. udevadm info --path=/class/block/sda is equivalent to udevadm info /sys/class/block/sda." }, { "flag": "-n", "long": null, "arg": null, "description": "The name of the device node or a symlink to query, e.g. [/dev/]/sda. This option is an alternative to the positional argument with a /dev/ prefix. udevadm info --name=sda is equivalent to udevadm info /dev/sda." }, { "flag": "-r", "long": "--root", "arg": null, "description": "Print absolute paths in name or symlink query." }, { "flag": "-a", "long": "--attribute-walk", "arg": null, "description": "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." }, { "flag": "-x", "long": "--export", "arg": null, "description": "Print output as key/value pairs. Values are enclosed in single quotes. This takes effects only when --query=property or --device-id-of-file=FILE is specified." }, { "flag": "-P", "long": null, "arg": null, "description": "Add a prefix to the key name of exported values. This implies --export." }, { "flag": "-d", "long": null, "arg": null, "description": "Print major/minor numbers of the underlying device, where the file lives on. If this is specified, all positional arguments are ignored." }, { "flag": "-e", "long": "--export-db", "arg": null, "description": "Export the content of the udev database." }, { "flag": "-c", "long": "--cleanup-db", "arg": null, "description": "Cleanup the udev database." }, { "flag": "", "long": null, "arg": null, "description": "Wait for device to be initialized. If argument SECONDS is not specified, the default is to wait forever." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Print a short help text and exit. The generated output shows the current device database entry in a terse format. Each line shown is prefixed with one of the following characters:" }, { "flag": "-v", "long": "--verbose", "arg": null, "description": "Print the list of devices which will be triggered." }, { "flag": "-n", "long": "--dry-run", "arg": null, "description": "Do not actually trigger the event." }, { "flag": "-q", "long": "--quiet", "arg": null, "description": "Suppress error logging in triggering events." }, { "flag": "-t", "long": null, "arg": null, "description": "Trigger a specific type of devices. Valid types are: devices, subsystems. The default value is devices." }, { "flag": "-c", "long": null, "arg": null, "description": "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\"." }, { "flag": "-s", "long": null, "arg": null, "description": "Trigger events for devices which belong to a 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." }, { "flag": "-S", "long": null, "arg": null, "description": "Do not trigger events for devices which belong to a matching subsystem. This option 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." }, { "flag": "-a", "long": null, "arg": null, "description": "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." }, { "flag": "-A", "long": null, "arg": null, "description": "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." }, { "flag": "-p", "long": null, "arg": null, "description": "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." }, { "flag": "-g", "long": null, "arg": null, "description": "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." }, { "flag": "-y", "long": null, "arg": null, "description": "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. --name-match=NAME 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." }, { "flag": "-b", "long": null, "arg": null, "description": "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." }, { "flag": "-w", "long": "--settle", "arg": null, "description": "Apart from triggering events, also waits for those events to finish. Note that this is different from calling udevadm settle. udevadm settle waits for all events to finish. This option only waits for events triggered by the same command to finish." }, { "flag": "", "long": "--uuid", "arg": null, "description": "Trigger the synthetic device events, and associate a randomized UUID with each. These UUIDs are printed to standard output, one line for each event. These UUIDs are included in the uevent environment block (in the \"SYNTHUUID=\" property) and may be used to track delivery of the generated events. --wait-daemon[=SECONDS] 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." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Print a short help text and exit. 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 [options] Watches the udev event queue, and exits if all current events are handled." }, { "flag": "-t", "long": null, "arg": null, "description": "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. A non-zero value will return an exit code of 0 if queue became empty before timeout was reached, non-zero otherwise." }, { "flag": "-E", "long": null, "arg": null, "description": "Stop waiting if file exists." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Print a short help text and exit. See systemd-udev-settle.service(8) for more information. udevadm control option Modify the internal state of the running udev daemon." }, { "flag": "-e", "long": "--exit", "arg": null, "description": "Signal and wait for systemd-udevd to exit. No option except for --timeout can be specified after this option. Note that systemd-udevd.service contains Restart=always 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" }, { "flag": "-l", "long": null, "arg": null, "description": "Set the internal log level of systemd-udevd. Valid values are the numerical syslog priorities or their textual representations: emerg, alert, crit, err, warning, notice, info, and debug." }, { "flag": "-s", "long": "--stop-exec-queue", "arg": null, "description": "Signal systemd-udevd to stop executing new events. Incoming events will be queued." }, { "flag": "-S", "long": "--start-exec-queue", "arg": null, "description": "Signal systemd-udevd to enable the execution of events." }, { "flag": "-R", "long": "--reload", "arg": null, "description": "Signal systemd-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." }, { "flag": "-p", "long": null, "arg": null, "description": "Set a global property for all events." }, { "flag": "-m", "long": null, "arg": null, "description": "Set the maximum number of events, systemd-udevd will handle at the same time." }, { "flag": "", "long": "--ping", "arg": null, "description": "Send a ping message to systemd-udevd and wait for the reply. This may be useful to check that systemd-udevd daemon is running." }, { "flag": "-t", "long": null, "arg": null, "description": "The maximum number of seconds to wait for a reply from systemd-udevd." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Print a short help text and exit. udevadm monitor [options] Listens 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." }, { "flag": "-k", "long": "--kernel", "arg": null, "description": "Print the kernel uevents." }, { "flag": "-u", "long": "--udev", "arg": null, "description": "Print the udev event after the rule processing." }, { "flag": "-p", "long": "--property", "arg": null, "description": "Also print the properties of the event." }, { "flag": "-s", "long": null, "arg": null, "description": "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." }, { "flag": "-t", "long": null, "arg": null, "description": "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." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Print a short help text and exit. udevadm test [options] [devpath] Simulate a udev event run for the given device, and print debug output." }, { "flag": "-a", "long": null, "arg": null, "description": "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\"." }, { "flag": "-N", "long": "--resolve-names", "arg": "early|late|never", "description": "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." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Print a short help text and exit. udevadm test-builtin [options] [command] [devpath] Run a built-in command COMMAND for device DEVPATH, and print debug output." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Print a short help text and exit." } ], "examples": [], "see_also": [ { "name": "udev", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/udev/7/json" }, { "name": "systemd-udevd.service", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/systemd-udevd.service/8/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 2, "subsections": [ { "name": "udevadm info [options] [devpath]", "lines": 1 }, { "name": "udevadm trigger [options] [devpath]", "lines": 1 }, { "name": "udevadm settle [options]", "lines": 2 }, { "name": "udevadm monitor [options]", "lines": 4 } ] }, { "name": "DESCRIPTION", "lines": 4, "subsections": [] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": "-d --debug", "lines": 3, "flag": "-d", "long": "--debug" }, { "name": "-h --help", "lines": 10, "flag": "-h", "long": "--help" }, { "name": "-q --query=", "lines": 3, "flag": "-q" }, { "name": "-p --path=", "lines": 4, "flag": "-p" }, { "name": "-n --name=", "lines": 4, "flag": "-n" }, { "name": "-r --root", "lines": 2, "flag": "-r", "long": "--root" }, { "name": "-a --attribute-walk", "lines": 4, "flag": "-a", "long": "--attribute-walk" }, { "name": "-x --export", "lines": 3, "flag": "-x", "long": "--export" }, { "name": "-P --export-prefix=", "lines": 2, "flag": "-P" }, { "name": "-d --device-id-of-file=", "lines": 3, "flag": "-d" }, { "name": "-e --export-db", "lines": 2, "flag": "-e", "long": "--export-db" }, { "name": "-c --cleanup-db", "lines": 2, "flag": "-c", "long": "--cleanup-db" }, { "name": "-w[SECONDS] --wait-for-initialization[=SECONDS]", "lines": 3 }, { "name": "-h --help", "lines": 5, "flag": "-h", "long": "--help" }, { "name": "Table 1. udevadm info output prefixes", "lines": 20 }, { "name": "-v --verbose", "lines": 2, "flag": "-v", "long": "--verbose" }, { "name": "-n --dry-run", "lines": 2, "flag": "-n", "long": "--dry-run" }, { "name": "-q --quiet", "lines": 2, "flag": "-q", "long": "--quiet" }, { "name": "-t --type=", "lines": 3, "flag": "-t" }, { "name": "-c --action=", "lines": 4, "flag": "-c" }, { "name": "-s --subsystem-match=", "lines": 4, "flag": "-s" }, { "name": "-S --subsystem-nomatch=", "lines": 5, "flag": "-S" }, { "name": "-a --attr-match=", "lines": 6, "flag": "-a" }, { "name": "-A --attr-nomatch=", "lines": 7, "flag": "-A" }, { "name": "-p --property-match=", "lines": 5, "flag": "-p" }, { "name": "-g --tag-match=", "lines": 4, "flag": "-g" }, { "name": "-y --sysname-match=", "lines": 10, "flag": "-y" }, { "name": "-b --parent-match=", "lines": 4, "flag": "-b" }, { "name": "-w --settle", "lines": 4, "flag": "-w", "long": "--settle" }, { "name": "--uuid", "lines": 10, "long": "--uuid" }, { "name": "-h --help", "lines": 8, "flag": "-h", "long": "--help" }, { "name": "-t --timeout=", "lines": 5, "flag": "-t" }, { "name": "-E --exit-if-exists=", "lines": 2, "flag": "-E" }, { "name": "-h --help", "lines": 7, "flag": "-h", "long": "--help" }, { "name": "-e --exit", "lines": 8, "flag": "-e", "long": "--exit" }, { "name": "-l --log-level=", "lines": 4, "flag": "-l" }, { "name": "-s --stop-exec-queue", "lines": 2, "flag": "-s", "long": "--stop-exec-queue" }, { "name": "-S --start-exec-queue", "lines": 2, "flag": "-S", "long": "--start-exec-queue" }, { "name": "-R --reload", "lines": 4, "flag": "-R", "long": "--reload" }, { "name": "-p --property=", "lines": 2, "flag": "-p" }, { "name": "-m --children-max=", "lines": 2, "flag": "-m" }, { "name": "--ping", "lines": 3, "long": "--ping" }, { "name": "-t --timeout=", "lines": 2, "flag": "-t" }, { "name": "-h --help", "lines": 7, "flag": "-h", "long": "--help" }, { "name": "-k --kernel", "lines": 2, "flag": "-k", "long": "--kernel" }, { "name": "-u --udev", "lines": 2, "flag": "-u", "long": "--udev" }, { "name": "-p --property", "lines": 2, "flag": "-p", "long": "--property" }, { "name": "-s --subsystem-match=", "lines": 4, "flag": "-s" }, { "name": "-t --tag-match=", "lines": 4, "flag": "-t" }, { "name": "-h --help", "lines": 5, "flag": "-h", "long": "--help" }, { "name": "-a --action=", "lines": 4, "flag": "-a" }, { "name": "-N --resolve-names=early|late|never", "lines": 5, "flag": "-N", "long": "--resolve-names", "arg": "early|late|never" }, { "name": "-h --help", "lines": 5, "flag": "-h", "long": "--help" }, { "name": "-h --help", "lines": 2, "flag": "-h", "long": "--help" } ] }, { "name": "SEE ALSO", "lines": 5, "subsections": [] } ], "sections": { "NAME": { "content": "udevadm - udev management tool\n", "subsections": [] }, "SYNOPSIS": { "content": "udevadm [--debug] [--version] [--help]\n", "subsections": [ { "name": "udevadm info [options] [devpath]", "content": "" }, { "name": "udevadm trigger [options] [devpath]", "content": "" }, { "name": "udevadm settle [options]", "content": "udevadm control option\n" }, { "name": "udevadm monitor [options]", "content": "udevadm test [options] devpath\n\nudevadm test-builtin [options] command devpath\n" } ] }, "DESCRIPTION": { "content": "udevadm expects a command and command specific options. It controls the runtime behavior of\nsystemd-udevd, requests kernel events, manages the event queue, and provides simple debugging\nmechanisms.\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-d --debug", "content": "Print debug messages to standard error. This option is implied in udevadm test and\nudevadm test-builtin commands.\n", "flag": "-d", "long": "--debug" }, { "name": "-h --help", "content": "Print a short help text and exit.\n\nudevadm info [options] [devpath|file|unit...]\nQuery the udev database for device information.\n\nPositional arguments should be used to specify one or more devices. Each one may be a device\nname (in which case it must start with /dev/), a sys path (in which case it must start with\n/sys/), or a systemd device unit name (in which case it must end with \".device\", see\nsystemd.device(5)).\n", "flag": "-h", "long": "--help" }, { "name": "-q --query=", "content": "Query the database for the specified type of device data. Valid TYPEs are: name, symlink,\npath, property, all.\n", "flag": "-q" }, { "name": "-p --path=", "content": "The /sys/ path of the device to query, e.g. [/sys/]/class/block/sda. This option is an\nalternative to the positional argument with a /sys/ prefix. udevadm info\n--path=/class/block/sda is equivalent to udevadm info /sys/class/block/sda.\n", "flag": "-p" }, { "name": "-n --name=", "content": "The name of the device node or a symlink to query, e.g. [/dev/]/sda. This option is an\nalternative to the positional argument with a /dev/ prefix. udevadm info --name=sda is\nequivalent to udevadm info /dev/sda.\n", "flag": "-n" }, { "name": "-r --root", "content": "Print absolute paths in name or symlink query.\n", "flag": "-r", "long": "--root" }, { "name": "-a --attribute-walk", "content": "Print all sysfs properties of the specified device that can be used in udev rules to\nmatch the specified device. It prints all devices along the chain, up to the root of\nsysfs that can be used in udev rules.\n", "flag": "-a", "long": "--attribute-walk" }, { "name": "-x --export", "content": "Print output as key/value pairs. Values are enclosed in single quotes. This takes effects\nonly when --query=property or --device-id-of-file=FILE is specified.\n", "flag": "-x", "long": "--export" }, { "name": "-P --export-prefix=", "content": "Add a prefix to the key name of exported values. This implies --export.\n", "flag": "-P" }, { "name": "-d --device-id-of-file=", "content": "Print major/minor numbers of the underlying device, where the file lives on. If this is\nspecified, all positional arguments are ignored.\n", "flag": "-d" }, { "name": "-e --export-db", "content": "Export the content of the udev database.\n", "flag": "-e", "long": "--export-db" }, { "name": "-c --cleanup-db", "content": "Cleanup the udev database.\n", "flag": "-c", "long": "--cleanup-db" }, { "name": "-w[SECONDS] --wait-for-initialization[=SECONDS]", "content": "Wait for device to be initialized. If argument SECONDS is not specified, the default is\nto wait forever.\n" }, { "name": "-h --help", "content": "Print a short help text and exit.\n\nThe generated output shows the current device database entry in a terse format. Each line\nshown is prefixed with one of the following characters:\n", "flag": "-h", "long": "--help" }, { "name": "Table 1. udevadm info output prefixes", "content": "┌───────┬──────────────────────────────┐\n│Prefix │ Meaning │\n├───────┼──────────────────────────────┤\n│\"P:\" │ Device path in /sys/ │\n├───────┼──────────────────────────────┤\n│\"N:\" │ Kernel device node name │\n├───────┼──────────────────────────────┤\n│\"L:\" │ Device node symlink priority │\n├───────┼──────────────────────────────┤\n│\"S:\" │ Device node symlink │\n├───────┼──────────────────────────────┤\n│\"E:\" │ Device property │\n└───────┴──────────────────────────────┘\n\nudevadm trigger [options] [devpath|file|unit]\nRequest device events from the kernel. Primarily used to replay events at system coldplug\ntime.\n\nTakes device specifications as positional arguments. See the description of info above.\n" }, { "name": "-v --verbose", "content": "Print the list of devices which will be triggered.\n", "flag": "-v", "long": "--verbose" }, { "name": "-n --dry-run", "content": "Do not actually trigger the event.\n", "flag": "-n", "long": "--dry-run" }, { "name": "-q --quiet", "content": "Suppress error logging in triggering events.\n", "flag": "-q", "long": "--quiet" }, { "name": "-t --type=", "content": "Trigger a specific type of devices. Valid types are: devices, subsystems. The default\nvalue is devices.\n", "flag": "-t" }, { "name": "-c --action=", "content": "Type of event to be triggered. Possible actions are \"add\", \"remove\", \"change\", \"move\",\n\"online\", \"offline\", \"bind\", and \"unbind\". Also, the special value \"help\" can be used to\nlist the possible actions. The default value is \"change\".\n", "flag": "-c" }, { "name": "-s --subsystem-match=", "content": "Trigger events for devices which belong to a matching subsystem. This option supports\nshell style pattern matching. When this option is specified more than once, then each\nmatching result is ORed, that is, all the devices in each subsystem are triggered.\n", "flag": "-s" }, { "name": "-S --subsystem-nomatch=", "content": "Do not trigger events for devices which belong to a matching subsystem. This option\nsupports shell style pattern matching. When this option is specified more than once, then\neach matching result is ANDed, that is, devices which do not match all specified\nsubsystems are triggered.\n", "flag": "-S" }, { "name": "-a --attr-match=", "content": "Trigger events for devices with a matching sysfs attribute. If a value is specified along\nwith the attribute name, the content of the attribute is matched against the given value\nusing shell style pattern matching. If no value is specified, the existence of the sysfs\nattribute is checked. When this option is specified multiple times, then each matching\nresult is ANDed, that is, only devices which have all specified attributes are triggered.\n", "flag": "-a" }, { "name": "-A --attr-nomatch=", "content": "Do not trigger events for devices with a matching sysfs attribute. If a value is\nspecified along with the attribute name, the content of the attribute is matched against\nthe given value using shell style pattern matching. If no value is specified, the\nexistence of the sysfs attribute is checked. When this option is specified multiple\ntimes, then each matching result is ANDed, that is, only devices which have none of the\nspecified attributes are triggered.\n", "flag": "-A" }, { "name": "-p --property-match=", "content": "Trigger events for devices with a matching property value. This option supports shell\nstyle pattern matching. When this option is specified more than once, then each matching\nresult is ORed, that is, devices which have one of the specified properties are\ntriggered.\n", "flag": "-p" }, { "name": "-g --tag-match=", "content": "Trigger events for devices with a matching tag. When this option is specified multiple\ntimes, then each matching result is ANDed, that is, devices which have all specified tags\nare triggered.\n", "flag": "-g" }, { "name": "-y --sysname-match=", "content": "Trigger events for devices for which the last component (i.e. the filename) of the /sys/\npath matches the specified PATH. This option supports shell style pattern matching. When\nthis option is specified more than once, then each matching result is ORed, that is, all\ndevices which have any of the specified NAME are triggered.\n\n--name-match=NAME\nTrigger events for devices with a matching device path. When this option is specified\nmore than once, then each matching result is ORed, that is, all specified devices are\ntriggered.\n", "flag": "-y" }, { "name": "-b --parent-match=", "content": "Trigger events for all children of a given device. When this option is specified more\nthan once, then each matching result is ORed, that is, all children of each specified\ndevice are triggered.\n", "flag": "-b" }, { "name": "-w --settle", "content": "Apart from triggering events, also waits for those events to finish. Note that this is\ndifferent from calling udevadm settle. udevadm settle waits for all events to finish.\nThis option only waits for events triggered by the same command to finish.\n", "flag": "-w", "long": "--settle" }, { "name": "--uuid", "content": "Trigger the synthetic device events, and associate a randomized UUID with each. These\nUUIDs are printed to standard output, one line for each event. These UUIDs are included\nin the uevent environment block (in the \"SYNTHUUID=\" property) and may be used to track\ndelivery of the generated events.\n\n--wait-daemon[=SECONDS]\nBefore triggering uevents, wait for systemd-udevd daemon to be initialized. Optionally\ntakes timeout value. Default timeout is 5 seconds. This is equivalent to invoke invoking\nudevadm control --ping before udevadm trigger.\n", "long": "--uuid" }, { "name": "-h --help", "content": "Print a short help text and exit.\n\nIn addition, optional positional arguments can be used to specify device names or sys paths.\nThey must start with /dev/ or /sys/ respectively.\n\nudevadm settle [options]\nWatches the udev event queue, and exits if all current events are handled.\n", "flag": "-h", "long": "--help" }, { "name": "-t --timeout=", "content": "Maximum number of seconds to wait for the event queue to become empty. The default value\nis 120 seconds. A value of 0 will check if the queue is empty and always return\nimmediately. A non-zero value will return an exit code of 0 if queue became empty before\ntimeout was reached, non-zero otherwise.\n", "flag": "-t" }, { "name": "-E --exit-if-exists=", "content": "Stop waiting if file exists.\n", "flag": "-E" }, { "name": "-h --help", "content": "Print a short help text and exit.\n\nSee systemd-udev-settle.service(8) for more information.\n\nudevadm control option\nModify the internal state of the running udev daemon.\n", "flag": "-h", "long": "--help" }, { "name": "-e --exit", "content": "Signal and wait for systemd-udevd to exit. No option except for --timeout can be\nspecified after this option. Note that systemd-udevd.service contains Restart=always and\nso as a result, this option restarts systemd-udevd. If you want to stop\nsystemd-udevd.service, please use the following:\n\nsystemctl stop systemd-udevd-control.socket systemd-udevd-kernel.socket systemd-udevd.service\n\n", "flag": "-e", "long": "--exit" }, { "name": "-l --log-level=", "content": "Set the internal log level of systemd-udevd. Valid values are the numerical syslog\npriorities or their textual representations: emerg, alert, crit, err, warning, notice,\ninfo, and debug.\n", "flag": "-l" }, { "name": "-s --stop-exec-queue", "content": "Signal systemd-udevd to stop executing new events. Incoming events will be queued.\n", "flag": "-s", "long": "--stop-exec-queue" }, { "name": "-S --start-exec-queue", "content": "Signal systemd-udevd to enable the execution of events.\n", "flag": "-S", "long": "--start-exec-queue" }, { "name": "-R --reload", "content": "Signal systemd-udevd to reload the rules files and other databases like the kernel module\nindex. Reloading rules and databases does not apply any changes to already existing\ndevices; the new configuration will only be applied to new events.\n", "flag": "-R", "long": "--reload" }, { "name": "-p --property=", "content": "Set a global property for all events.\n", "flag": "-p" }, { "name": "-m --children-max=", "content": "Set the maximum number of events, systemd-udevd will handle at the same time.\n", "flag": "-m" }, { "name": "--ping", "content": "Send a ping message to systemd-udevd and wait for the reply. This may be useful to check\nthat systemd-udevd daemon is running.\n", "long": "--ping" }, { "name": "-t --timeout=", "content": "The maximum number of seconds to wait for a reply from systemd-udevd.\n", "flag": "-t" }, { "name": "-h --help", "content": "Print a short help text and exit.\n\nudevadm monitor [options]\nListens to the kernel uevents and events sent out by a udev rule and prints the devpath of\nthe event to the console. It can be used to analyze the event timing, by comparing the\ntimestamps of the kernel uevent and the udev event.\n", "flag": "-h", "long": "--help" }, { "name": "-k --kernel", "content": "Print the kernel uevents.\n", "flag": "-k", "long": "--kernel" }, { "name": "-u --udev", "content": "Print the udev event after the rule processing.\n", "flag": "-u", "long": "--udev" }, { "name": "-p --property", "content": "Also print the properties of the event.\n", "flag": "-p", "long": "--property" }, { "name": "-s --subsystem-match=", "content": "Filter kernel uevents and udev events by subsystem[/devtype]. Only events with a matching\nsubsystem value will pass. When this option is specified more than once, then each\nmatching result is ORed, that is, all devices in the specified subsystems are monitored.\n", "flag": "-s" }, { "name": "-t --tag-match=", "content": "Filter udev events by tag. Only udev events with a given tag attached will pass. When\nthis option is specified more than once, then each matching result is ORed, that is,\ndevices which have one of the specified tags are monitored.\n", "flag": "-t" }, { "name": "-h --help", "content": "Print a short help text and exit.\n\nudevadm test [options] [devpath]\nSimulate a udev event run for the given device, and print debug output.\n", "flag": "-h", "long": "--help" }, { "name": "-a --action=", "content": "Type of event to be simulated. Possible actions are \"add\", \"remove\", \"change\", \"move\",\n\"online\", \"offline\", \"bind\", and \"unbind\". Also, the special value \"help\" can be used to\nlist the possible actions. The default value is \"add\".\n", "flag": "-a" }, { "name": "-N --resolve-names=early|late|never", "content": "Specify when udevadm should resolve names of users and groups. When set to early (the\ndefault), names will be resolved when the rules are parsed. When set to late, names will\nbe resolved for every event. When set to never, names will never be resolved and all\ndevices will be owned by root.\n", "flag": "-N", "long": "--resolve-names", "arg": "early|late|never" }, { "name": "-h --help", "content": "Print a short help text and exit.\n\nudevadm test-builtin [options] [command] [devpath]\nRun a built-in command COMMAND for device DEVPATH, and print debug output.\n", "flag": "-h", "long": "--help" }, { "name": "-h --help", "content": "Print a short help text and exit.\n", "flag": "-h", "long": "--help" } ] }, "SEE ALSO": { "content": "udev(7), systemd-udevd.service(8)\n\n\n\nsystemd 249 UDEVADM(8)", "subsections": [] } } } }