From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] cman: Update cman_tool version section in man page
Date: Wed, 12 Jan 2011 16:28:24 +0100 [thread overview]
Message-ID: <4D2DC898.3070709@redhat.com> (raw)
In-Reply-To: <1294844219-7065-1-git-send-email-lhh@redhat.com>
ACK?ed.
Fabio
On 1/12/2011 3:56 PM, Lon Hohberger wrote:
> This is a clean cherry-pick to the RHEL6 branch
>
> Resolves: rhbz#619874
>
> Signed-off-by: Lon Hohberger <lhh@redhat.com>
> ---
> cman/man/cman_tool.8 | 13 +++++--------
> 1 files changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/cman/man/cman_tool.8 b/cman/man/cman_tool.8
> index 5d38941..bd710a2 100644
> --- a/cman/man/cman_tool.8
> +++ b/cman/man/cman_tool.8
> @@ -65,15 +65,12 @@ you need to get it running again in a hurry.
> .I version
> Used alone this will report the major, minor, patch and config versions
> used by CMAN (also displayed in 'cman_tool status'). It can also be used
> -with -r to tell cluster members to update.
> +with -r to tell cluster members to update the cluster configuration.
> .br
> -The argument to -r is the version number that cman should look for. If
> -that version is not currently available then cman will poll for it. If
> -a version of 0 is specified then cman will read the configuration file,
> -validate it, distribute it around the cluster (if necessary) and
> -activate it.
> -.br
> -The -D flag can disable the validation stage. This is NOT recommended.
> +If -r is specified, cman will read the configuration file,
> +validate it, distribute it around the cluster (if necessary) an
> +activate it. See the VERSION OPTIONS section below for additional
> +options to the \fBversion\fP command.
>
> .TP
> .I wait
next prev parent reply other threads:[~2011-01-12 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 14:56 [Cluster-devel] [PATCH] cman: Update cman_tool version section in man page Lon Hohberger
2011-01-12 15:28 ` Fabio M. Di Nitto [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-12 15:09 Lon Hohberger
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=4D2DC898.3070709@redhat.com \
--to=fdinitto@redhat.com \
/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).