From: cfeist@sourceware.org <cfeist@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster cman/init.d/cman fence/init.d/fenced
Date: 20 Dec 2006 18:36:12 -0000 [thread overview]
Message-ID: <20061220183612.17716.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: cfeist at sourceware.org 2006-12-20 18:36:12
Modified files:
cman/init.d : cman
fence/init.d : fenced
Log message:
- Fixed a small cman and fence init script bug which would cause error
messages about missing gulm messages to be prematurely cut. (#176378)
From cmarthal at redhat.com
Skipping because of <gulm> section detected in
/etc/cluster/cluster.conf"
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/init.d/cman.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.1.2.16&r2=1.1.2.17
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/init.d/fenced.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.1.2.8&r2=1.1.2.9
--- cluster/cman/init.d/cman 2006/05/08 22:30:58 1.1.2.16
+++ cluster/cman/init.d/cman 2006/12/20 18:36:11 1.1.2.17
@@ -55,8 +55,7 @@
elif grep -qE "<[[:space:]]*gulm([[:space:]]|[>]|$)" \
/etc/cluster/cluster.conf
then
- warning "Skipping because of <gulm> section detected in " \
- "/etc/cluster/cluster.conf"
+ warning "Skipping because of <gulm> section detected in /etc/cluster/cluster.conf"
echo
exit 0
fi
--- cluster/fence/init.d/Attic/fenced 2006/08/09 20:05:54 1.1.2.8
+++ cluster/fence/init.d/Attic/fenced 2006/12/20 18:36:11 1.1.2.9
@@ -34,8 +34,7 @@
elif grep -qE "<[[:space:]]*gulm([[:space:]]|[>]|$)" \
/etc/cluster/cluster.conf
then
- warning "Skipping because of <gulm> section detected in " \
- "/etc/cluster/cluster.conf"
+ warning "Skipping because of <gulm> section detected in /etc/cluster/cluster.conf"
echo
exit 0
fi
reply other threads:[~2006-12-20 18:36 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=20061220183612.17716.qmail@sourceware.org \
--to=cfeist@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.