From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman/man cman_tool.8
Date: 22 Aug 2007 13:39:59 -0000 [thread overview]
Message-ID: <20070822133959.20182.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: teigland at sourceware.org 2007-08-22 13:39:57
Modified files:
cman/man : cman_tool.8
Log message:
mention group_tool should be used instead of cman_tool services
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&r1=1.10&r2=1.11
--- cluster/cman/man/cman_tool.8 2007/08/22 09:34:16 1.10
+++ cluster/cman/man/cman_tool.8 2007/08/22 13:39:57 1.11
@@ -35,8 +35,8 @@
shutdown CLVM, fenced and anything else using the cluster manager before
using
.B cman_tool leave.
-Look at 'cman_tool status|services' to see how many (and which) services are
-running.
+Look at 'cman_tool status' and group_tool to see how many (and which)
+subsystems are active.
.br
When a node leaves the cluster, the remaining nodes recalculate quorum and this
may block cluster activity if the required number of votes is not present.
@@ -81,7 +81,8 @@
.TP
.I services
-Displays the local view of the cluster services.
+Displays the local view of subsystems using cman (deprecated, group_tool
+should be used instead).
.SH "LEAVE" OPTIONS
.TP
next reply other threads:[~2007-08-22 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 13:39 teigland [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-08 9:39 [Cluster-devel] cluster/cman/man cman_tool.8 pcaulfield
2007-11-08 9:36 pcaulfield
2007-10-12 18:53 rohara
2007-10-12 18:16 rohara
2007-09-25 20:10 teigland
2007-09-17 13:59 pcaulfield
2007-08-22 13:41 teigland
2007-08-22 9:34 pcaulfield
2007-08-22 9:34 pcaulfield
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=20070822133959.20182.qmail@sourceware.org \
--to=teigland@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 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 NNTP newsgroup(s).