From 32759d402e7327865ea18a203bd1c09f98735bd1 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sun, 22 Oct 2017 17:09:25 +0000 Subject: Initial commit --- doc/mdevd-coldplug.html | 74 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) create mode 100644 doc/mdevd-coldplug.html (limited to 'doc/mdevd-coldplug.html') diff --git a/doc/mdevd-coldplug.html b/doc/mdevd-coldplug.html new file mode 100644 index 0000000..8355df3 --- /dev/null +++ b/doc/mdevd-coldplug.html @@ -0,0 +1,74 @@ + + + + + + mdevd: the mdevd-coldplug program + + + + + + +

+mdevd
+Software
+skarnet.org +

+ +

The `mdevd-coldplug` program

+ +

+mdevd-coldplug performs a coldplug: it scans +/sys for all registered devices an uevent manager would +want to perform actions on, and generates uevents for all these +devices. +

+ +

Interface

+ +

+     mdevd-coldplug [ -s slashsys ]
+

+ +

mdevd-coldplug scans /sys for devices.
For every suitable device it finds, it generates an +uevent and writes it to its stdout, using the same format +as mdevd-netlink.
It exits when it has finished scanning.

+ +

+ This implies that the mdevd-coldplug | mdevd command line +will function as a coldplug manager, just like mdev -s. +

+ +

Options

+ +

-s slashsys : assume the sysfs +pseudo-filesystem is mounted on slashsys. Default is /sys.

+ +

Exit codes

+ +

0: success
111: system call failed

+ +

Notes

+ +

mdevd-coldplug is a short-lived program, just like +mdev -s.
Unlike mdev -s, however, mdevd-coldplug does +not act on the uevents it generates. It simply prints them. +This allows for easy debugging.
To act on the uevents, simply pipe the output of +mdevd-coldplug into mdevd.

+ + + -- cgit v1.3.1

The mdevd-coldplug program

Interface

Options

Exit codes

Notes

The `mdevd-coldplug` program