public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: ccaulfield@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW man/clvmd.8.in Date: Thu, 30 Jul 2009 13:32:00 -0000 [thread overview] Message-ID: <20090730133240.6783.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: ccaulfield@sourceware.org 2009-07-30 13:32:39 Modified files: . : WHATS_NEW man : clvmd.8.in Log message: Document the -I option to clvmd Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1211&r2=1.1212 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/clvmd.8.in.diff?cvsroot=lvm2&r1=1.1&r2=1.2 --- LVM2/WHATS_NEW 2009/07/30 12:25:42 1.1211 +++ LVM2/WHATS_NEW 2009/07/30 13:32:38 1.1212 @@ -1,5 +1,6 @@ Version 2.02.51 - ================================ + Document -I option of clvmd in the man page. Fix configure script to handle multiple clvmd selections. Fix lvm2app.pc installation filename. Remove pv_t, vg_t & lv_t handles from lib. Only liblvm uses them. --- LVM2/man/clvmd.8.in 2008/10/08 12:50:13 1.1 +++ LVM2/man/clvmd.8.in 2009/07/30 13:32:39 1.2 @@ -74,6 +74,14 @@ re-read the lvm configuration file. This command should be run whenever the devices on a cluster system are changed. .TP +.I \-I +Selects the cluster manager to use for locking and internal communications, +the available managers will be listed as part of the 'clvmd -h' output. +clvmd will use the first cluster manager that succeeds, and it checks them +in the order cman,gulm,corosync,openais. As it is quite possible to have +(eg) corosync and cman available on the same system you might have to +manually specify this option to override the search. +.TP .I \-V Display the version of the cluster LVM daemon. .SH SEE ALSO
reply other threads:[~2009-07-30 13:32 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090730133240.6783.qmail@sourceware.org \ --to=ccaulfield@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).