From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/ccs/man cluster.conf.5
Date: 29 Nov 2006 17:04:32 -0000 [thread overview]
Message-ID: <20061129170432.10788.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2006-11-29 17:04:32
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&r1=1.6&r2=1.7
--- cluster/ccs/man/cluster.conf.5 2006/11/29 16:28:58 1.6
+++ cluster/ccs/man/cluster.conf.5 2006/11/29 17:04:31 1.7
@@ -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)
next reply other threads:[~2006-11-29 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 17:04 rpeterso [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-17 18:27 [Cluster-devel] cluster/ccs/man cluster.conf.5 teigland
2006-11-29 17:05 rpeterso
2006-11-29 17:05 rpeterso
2006-11-29 16:33 rpeterso
2006-11-29 16:30 rpeterso
2006-11-29 16:28 rpeterso
2006-07-25 20:20 rpeterso
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=20061129170432.10788.qmail@sourceware.org \
--to=rpeterso@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).