[Cluster-devel] cluster/ccs/man cluster.conf.5

[rpeterso at sourceware.org]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	rpeterso at sourceware.org	2006-11-29 17:05:20

Modified files:
	ccs/man        : cluster.conf.5 

Log message:
	Resolves: bz217436: Several updates needed to cluster.conf man page.
	1. Removed references to gulm.
	2. Other misc changes.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/ccs/man/cluster.conf.5.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.5.2.1&r2=1.5.2.2

--- cluster/ccs/man/cluster.conf.5	2006/11/29 16:30:30	1.5.2.1
+++ cluster/ccs/man/cluster.conf.5	2006/11/29 17:05:19	1.5.2.2
@@ -19,10 +19,8 @@
 This man page describes the generic contents of the \fBcluster.conf\fP file.
 The product specific sections of \fBcluster.conf\fP are left to their
 respective man pages.  For example, after constructing the generic content,
-a user should look at the \fBlock_gulmd(5)\fP man page for specific instructions
-if using lock_gulmd as their lock server.  Conversely, a user employing
-\fBcman\fP and the \fBdlm\fP locking protocol should look at \fBcman(5)\fP and \fBdlm(5)\fP for
-further instruction.
+a user should look at the \fBcman(5)\fP man page for further information
+about the \fBcman\fP section of cluster.conf.
 
 The \fBcluster.conf\fP file is an XML file.  It has one encompassing section
 in which everything is contained.  That entity's name is \fIcluster\fP and it
@@ -37,8 +35,8 @@
 
 </cluster>
 
-The users should specify a <cman/> tag or a <gulm/> tag to indicate the
-locking protocol used for the cluster.
+You should specify a <cman/> tag even if no special cman parameters
+are needed for the cluster.
 
 A mandatory subsection of \fIcluster\fP is \fIfencedevices\fP.  It contains
 all of the I/O fencing devices at the disposal of the cluster.  The I/O
@@ -220,5 +218,5 @@
 carefully.
 
 .SH SEE ALSO
-ccs(7), ccs_tool(8), lock_gulmd(5), cman(5)
+ccs(7), ccs_tool(8), cman(5)