A.3.2. Commands and Interfaces that Support udev
dmsetupcommands that support
Table A.2. dmsetup Commands to Support udev
| Used to notify that udev has completed processing the rules and unlocks waiting process (called from within |
|Used for debugging purposes to manually unlock all waiting processes.|
|Used for debugging purposes, to show all existing cookies (system-wide semaphores).|
|Used to create a cookie (semaphore) manually. This is useful to run more processes under one synchronization resource.|
| Used to wait for all |
dmsetupoptions that support
udevintegration are as follows.
- Needs to be defined for all dmsetup processes we would like to add into a udev transaction. It is used in conjunction with
COOKIE=$(dmsetup udevcreatecookie) dmsetup command --udevcookie $COOKIE .... dmsetup command --udevcookie $COOKIE .... .... dmsetup command --udevcookie $COOKIE .... dmsetup udevreleasecookie --udevcookie $COOKIEBesides using the
--udevcookieoption, you can just export the variable into an environment of the process:
export DM_UDEV_COOKIE=$(dmsetup udevcreatecookie) dmsetup command ... dmsetup command ... ... dmsetup command ...
- Disables udev rules. Nodes/symlinks will be created by
libdevmapperitself (the old way). This option is for debugging purposes, if
udevdoes not work correctly.
udevsynchronization. This is also for debugging purposes.
dmsetupand its options, see the
dmsetup(8) man page.
--noudevrules: as for the
--noudevsync: as for the
lvm.conffile includes the following options that support
udev_rulesfor all LVM2 commands globally.
udevsynchronization for all LVM commands globally.
lvm.conffile options, see the inline comments in the