cluster: STABLE3 - cman: add some explanation to cman_tool man page

cluster: STABLE3 - cman: add some explanation to cman_tool man page

[Christine Caulfield]

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.