.ad l
The hotplug2 application allows automatical loading of modules, based on the events sent by kernel, which can be invoked artifically (eg. using udevtrigger).
The purpose of hotplug2 is not to be a replacement of udev, instead it should be helpful during hardware autodetection in initrd / initramfs.
--coldplug, --no-coldplug Run or do not run coldplug application after starting hotplug2. Default is to run coldplug. Coldplug is what handles initial device probing. Separate application is reasonable, as you may want to use eg. a shell script for this purpose instead.
--persistent, --no-persistent Keep hotplug2 running even after all events have been processed, waiting for more. The default behavior is not to be persistent: note that it will still block until at least one event has been processed.
--dumb, --no-dumb Run or do not run hotplug2 in dumb mode. Dumb mode means that rules are being ignored, the only action taken is mload modules to all devices whose uevent exports MODALIAS. Only available if compiled with HAVE_RULES.
--max-children <value> Set the value of maximum children hotplug2 may have running simultaneously. Default is 20.
--set-coldplug-cmd <cmd> Sets the application used to perform coldplug. Default is '/sbin/udevtrigger'. Is executed using execvp() call.
--set-modprobe-cmd <cmd> Sets the application used to perform modprobe. It only gets used in dumb mode. Default is to autodetect: if '/bin/modprobe' is from module-init-tools, use '/sbin/modprobe', otherwise use '/sbin/hotplug2-modwrap'.
SIGUSR1 The USR1 signal makes hotplug2 switch persistency mode from persistent to non-persistent and vice versa. If the mode is switched to non-persistent and it appears that all events already sent were processed, hotplug2 terminates itself.
Written by iSteve <isteve@bofh.cz>
udev(7), udevd(8), udevinfo(8), udevmonitor(8)