public inbox for
help / color / mirror / Atom feed
Subject: LVM2/man
Date: Mon, 15 Feb 2010 16:32:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	2010-02-15 16:32:24

Modified files:
	man            : 

Log message:
	Update man page for dmsetup: --udevcookie, udevcreatecookie and udevreleasecookie.


--- LVM2/man/	2010/01/07 19:45:12	1.30
+++ LVM2/man/	2010/02/15 16:32:24	1.31
@@ -64,6 +64,11 @@
 .B dmsetup mknodes
 .I [device_name]
+.B dmsetup udevcreatecookie
+.B dmsetup udevreleasecookie
+.I [cookie]
 .B dmsetup udevflags
 .I cookie
@@ -127,6 +132,9 @@
 .IP \fB--notable
 When creating a device, don't load any table.
+.IP \fB--udevcookie\ \fIcookie
+Use cookie for udev synchronisation.
 .IP \fB--noudevrules
 Do not allow udev to manage nodes for devices in device-mapper directory.
@@ -315,6 +323,26 @@
 Displays the names and versions of the currently-loaded targets.
+.IP \fBudevcreatecookie
+Creates a new cookie to synchronize actions with udev processing.
+The output is a cookie value. Normally we don't need to create cookies since
+dmsetup creates and destroys them for each action automatically. However, we can
+generate one explicitly to group several actions together and use only one
+cookie instead. We can define a cookie to use for each relevant command by using
+--udevcookie option. Alternatively, we can export this value into the environment
+of the dmsetup process as DM_UDEV_COOKIE variable and it will be used automatically
+with all subsequent commands until it is unset.
+Invoking this command will create system-wide semaphore that needs to be cleaned
+up explicitly by calling udevreleasecookie command.
+.IP \fBudevreleasecookie
+.I [cookie]
+Waits for all pending udev processing bound to given cookie value and clean up
+the cookie with underlying semaphore. If the cookie is not given directly,
+the command will try to use a value defined by DM_UDEV_COOKIE environment variable.
 .IP \fBudevflags
 .I cookie
@@ -412,6 +440,10 @@
 The device directory name.
 Defaults to "/dev" and must be an absolute path.
+A cookie to use for all relevant commands to synchronize with udev processing.
+It is an alternative to using --udevcookie option.
 Original version: Joe Thornber (

             reply	other threads:[~2010-02-15 16:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 16:32 prajnoha [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-15 12:25 prajnoha
2011-11-30 22:32 agk
2011-11-13  1:41 agk
2011-03-10 13:11 mbroz
2009-11-06  1:41 agk
2009-10-22 13:12 prajnoha
2009-04-23 12:20 agk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).