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 ./WHATS_NEW man/dmsetup.8.in Date: Fri, 11 Sep 2009 16:06:00 -0000 [thread overview] Message-ID: <20090911160632.4120.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: prajnoha@sourceware.org 2009-09-11 16:06:32 Modified files: . : WHATS_NEW man : dmsetup.8.in Log message: Add manpage entry for dmsetup's udevcomplete_all and udevcookies commands. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1258&r2=1.1259 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/dmsetup.8.in.diff?cvsroot=lvm2&r1=1.24&r2=1.25 --- LVM2/WHATS_NEW 2009/09/11 16:05:20 1.1258 +++ LVM2/WHATS_NEW 2009/09/11 16:06:31 1.1259 @@ -1,5 +1,6 @@ Version 2.02.52 - ================================= + Add manpage entry for dmsetup's udevcomplete_all and udevcookies commands. Add DM_UDEV_RULES_VSN udev enviroment variable. Check that udev is running and set internal state appropriately. Add libudev configuration check. --- LVM2/man/dmsetup.8.in 2009/07/31 17:51:46 1.24 +++ LVM2/man/dmsetup.8.in 2009/09/11 16:06:31 1.25 @@ -67,6 +67,10 @@ .B dmsetup udevcomplete .I cookie .br +.B dmsetup udevcomplete_all +.br +.B dmsetup udevcookies +.br .B dmsetup targets .br .B dmsetup version @@ -291,6 +295,13 @@ .br Wake any processes that are waiting for udev to complete processing the specified cookie. .br +.IP \fBudevcomplete_all +Remove all cookies. Any process waiting on a cookie will be resumed immediately. +.br +.IP \fBudevcookies +List all existing cookies. Cookies are system-wide semaphores with keys +prefixed by two predefined bytes (0x0D4D). +.br .IP \fBversion .br Outputs version information.
next reply other threads:[~2009-09-11 16:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-11 16:06 prajnoha [this message] 2010-03-09 13:42 agk 2010-05-27 19:00 snitzer
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=20090911160632.4120.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).