public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: fabbione@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 WHATS_NEW configure.in Date: Mon, 13 Feb 2012 05:25:00 -0000 [thread overview] Message-ID: <20120213052458.28874.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: fabbione@sourceware.org 2012-02-13 05:24:58 Modified files: . : WHATS_NEW configure.in Log message: In the new corosync world, dlm is a standalone service. Fix clvmd init script to Require dlm service when building for the new corosync or clvmd will fail to start. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2279&r2=1.2280 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/configure.in.diff?cvsroot=lvm2&r1=1.180&r2=1.181 --- LVM2/WHATS_NEW 2012/02/13 00:23:21 1.2279 +++ LVM2/WHATS_NEW 2012/02/13 05:24:57 1.2280 @@ -1,5 +1,6 @@ Version 2.02.92 - ==================================== + Add clvmd init dependency on dlm service when running with new corosync. Version 2.02.91 - 12th February 2012 ==================================== --- LVM2/configure.in 2012/01/31 21:21:54 1.180 +++ LVM2/configure.in 2012/02/13 05:24:57 1.181 @@ -675,6 +675,15 @@ fi fi +dnl -- Fixup CLVMD_CMANAGERS with new corosync +dnl -- clvmd built with corosync >= 2.0 needs dlm (either init or systemd service) +dnl -- to be started. +if [[ `expr x"$CLVMD" : '.*corosync.*'` != 0 ]]; then + if test x$HAVE_CMAP = xyes; then + CLVMD_CMANAGERS="$CLVMD_CMANAGERS dlm" + fi +fi + ################################################################################ dnl -- clvmd pidfile if test "x$CLVMD" != xnone; then
next reply other threads:[~2012-02-13 5:25 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-13 5:25 fabbione [this message] -- strict thread matches above, loose matches on Subject: below -- 2010-03-04 9:46 zkabelac 2009-09-11 15:55 prajnoha 2009-01-29 15:23 ccaulfield 2008-07-24 14:54 meyering 2008-06-23 9:23 meyering
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=20120213052458.28874.qmail@sourceware.org \ --to=fabbione@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).