public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: prajnoha@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/man dmsetup.8.in Date: Mon, 15 Feb 2010 16:32:00 -0000 [thread overview] Message-ID: <20100215163224.1391.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: prajnoha@sourceware.org 2010-02-15 16:32:24 Modified files: man : dmsetup.8.in Log message: Update man page for dmsetup: --udevcookie, udevcreatecookie and udevreleasecookie. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/dmsetup.8.in.diff?cvsroot=lvm2&r1=1.30&r2=1.31 --- LVM2/man/dmsetup.8.in 2010/01/07 19:45:12 1.30 +++ LVM2/man/dmsetup.8.in 2010/02/15 16:32:24 1.31 @@ -64,6 +64,11 @@ .B dmsetup mknodes .I [device_name] .br +.B dmsetup udevcreatecookie +.br +.B dmsetup udevreleasecookie +.I [cookie] +.br .B dmsetup udevflags .I cookie .br @@ -127,6 +132,9 @@ .IP \fB--notable .br When creating a device, don't load any table. +.IP \fB--udevcookie\ \fIcookie +.br +Use cookie for udev synchronisation. .IP \fB--noudevrules Do not allow udev to manage nodes for devices in device-mapper directory. .br @@ -315,6 +323,26 @@ .br Displays the names and versions of the currently-loaded targets. .br +.IP \fBudevcreatecookie +.br +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. +.br +.IP \fBudevreleasecookie +.I [cookie] +.br +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. +.br .IP \fBudevflags .I cookie .br @@ -412,6 +440,10 @@ \fBDM_DEV_DIR\fP The device directory name. Defaults to "/dev" and must be an absolute path. +.TP +\fBDM_UDEV_COOKIE\fP +A cookie to use for all relevant commands to synchronize with udev processing. +It is an alternative to using --udevcookie option. .SH AUTHORS Original version: Joe Thornber (thornber@sistina.com)
next 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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100215163224.1391.qmail@sourceware.org \ --to=prajnoha@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe 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).