public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: Christine Caulfield <chrissie@fedoraproject.org> To: cluster-cvs-relay@redhat.com Subject: cluster: STABLE3 - cman: add some explanation to cman_tool man page Date: Fri, 04 Sep 2009 12:28:00 -0000 [thread overview] Message-ID: <20090904122755.5367F120268@lists.fedorahosted.org> (raw) Gitweb: http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=12d9a6d70ce484adfcfed24716ad4b03dbd7c1a7 Commit: 12d9a6d70ce484adfcfed24716ad4b03dbd7c1a7 Parent: a5de3f2eb0585ad00571e513e15c7c2618cc4464 Author: Christine Caulfield <ccaulfie@redhat.com> AuthorDate: Fri Sep 4 13:26:36 2009 +0100 Committer: Christine Caulfield <ccaulfie@redhat.com> CommitterDate: Fri Sep 4 13:26:36 2009 +0100 cman: add some explanation to cman_tool man page Mention the fact that /cman/nodename can appear in ccs_dump, but not to worry about it. Signed-off-by: Christine Caulfield <ccaulfie@redhat.com> --- cman/man/cman_tool.8 | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/cman/man/cman_tool.8 b/cman/man/cman_tool.8 index 841586a..8d45048 100644 --- a/cman/man/cman_tool.8 +++ b/cman/man/cman_tool.8 @@ -411,3 +411,8 @@ for the details. Note that cmanpreconfig will not overwrite corosync keys that are explicitly set in the configuration file, allowing you to provide custom values for token timeouts etc, even though cman has its own defaults for some of those values. The exception to this is the node name/address and multicast values, which are always taken from the cman configuration keys. +.br +Most of the extra keys that cmanpreconfig adds are outside of the /cluster/ tree and will only be seen if you dump the whole of +corosync's object database. However it does add some keys into /cluster/cman that you would not normally see in a normal cluster.conf +file. These are harmless, though could be confusing. The most obvious of these is the "nodename" option which is passed from +cmanpreconfig to the name cman module, to save it recalculating the node name again.
reply other threads:[~2009-09-04 12:28 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=20090904122755.5367F120268@lists.fedorahosted.org \ --to=chrissie@fedoraproject.org \ --cc=cluster-cvs-relay@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: 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).