From: rohara@sourceware.org <rohara@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman/man cman_tool.8
Date: 12 Oct 2007 18:16:30 -0000 [thread overview]
Message-ID: <20071012181630.23158.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: rohara at sourceware.org 2007-10-12 18:16:30
Modified files:
cman/man : cman_tool.8
Log message:
Update man page to explain 'cman_tool nodes' filter/format options.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.4.2.5&r2=1.4.2.6
--- cluster/cman/man/cman_tool.8 2007/09/25 20:10:12 1.4.2.5
+++ cluster/cman/man/cman_tool.8 2007/10/12 18:16:30 1.4.2.6
@@ -130,7 +130,6 @@
Dictates the maximum amount of time cman_tool is prepared to wait.
If the operation times out then a status of 2 is returned.
-.br
.SH "JOIN" OPTIONS
.TP
.I -X
@@ -219,6 +218,17 @@
Note that just because cman_tool has given up, does not mean that cman itself
has stopped trying to join a cluster.
+.SH "NODES" OPTIONS
+.TP
+.I -n <nodename>
+Shows node information for a specific node. This should be the unqualified node
+name as it appears in 'cman_tool nodes'.
+.TP
+.I -F <format>
+Specify the format of the output. The format string may contain one or
+more format options, each seperated by a comma. Valid format options
+include: id, name, type, and addr.
+
.br
.SH "SERVICES" OUTPUT
next reply other threads:[~2007-10-12 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 18:16 rohara [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-09-25 20:10 teigland
2007-09-17 13:59 pcaulfield
2007-08-22 13:41 teigland
2007-08-22 13:39 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=20071012181630.23158.qmail@sourceware.org \
--to=rohara@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).