cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman/man cman.5
Date: 22 Aug 2007 15:48:04 -0000	[thread overview]
Message-ID: <20070822154804.17052.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	pcaulfield at sourceware.org	2007-08-22 15:48:03

Modified files:
	cman/man       : cman.5 

Log message:
	Add openais.conf information to man page

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman.5.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.6.2.2&r2=1.6.2.3

--- cluster/cman/man/cman.5	2007/08/22 15:13:37	1.6.2.2
+++ cluster/cman/man/cman.5	2007/08/22 15:48:03	1.6.2.3
@@ -136,10 +136,49 @@
 .in -7
 
 
+\fIOther OpenAIS parameters\fR
+.in +7
+In addition to the cman-specific sections, cman also loads in configuration for openAIS from CCS from the following keys:
+
+<totem>
+<logging>
+<event>
+<aisexec>
+<group>
+
+See the 
+.B openais.conf(5)
+man page for more information on keys that are valid for these sections. 
+Note that the <clusternodes> section will overwrite things in these sections 
+and options on the cman_tool command line will override both. 
+In particular setting things like bindnetaddr, mcastaddr, mcastport & 
+nodeid in this section will always be replaced by the values in <clusternodes>.
+
+cman does not use the openais.conf file at all. What it does do is 
+load the values from CCS into internal OpenAIS data structures that 
+map onto the entries to openais.conf. So that's why you can add an 
+entry in a <totem> section in CCS and it will be used by totem.
+
+Here's how to increase the token timeout to five seconds:
+
+  <totem token="5000"/>
+
+And this is how to add extra AIS logging options to cman & CPG:
+
+  <logging to_stderr="yes">
+    <logger ident="CPG" debug="on" to_stderr="yes">
+    </logger>
+    <logger ident="CMAN" debug="on" to_stderr="yes">
+    </logger>
+  </logging>
+
+.in -7
+
+
 
 .sp
 .in -7
 \fBSEE ALSO\fP
 .in +7
-cluster.conf(5), ccs(7), cman_tool(8)
+cluster.conf(5), openais.conf(5), ccs(7), cman_tool(8)
 



             reply	other threads:[~2007-08-22 15:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 15:48 pcaulfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-23 14:40 [Cluster-devel] cluster/cman/man cman.5 teigland
2007-08-23 14:37 teigland
2007-08-23  8:43 pcaulfield
2007-08-23  8:42 pcaulfield
2007-08-22 15:43 pcaulfield
2007-08-22 15:13 pcaulfield
2007-08-22 15:13 teigland
2007-08-22 15:13 teigland
2007-08-22  8:36 pcaulfield
2007-08-22  8:35 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=20070822154804.17052.qmail@sourceware.org \
    --to=pcaulfield@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).