From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/fence/man fence_node.8
Date: 22 Aug 2007 14:21:14 -0000 [thread overview]
Message-ID: <20070822142114.13975.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: teigland at sourceware.org 2007-08-22 14:21:14
Modified files:
fence/man : fence_node.8
Log message:
this was missed in the big man page update from HEAD
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/man/fence_node.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.7&r2=1.7.2.1
--- cluster/fence/man/fence_node.8 2005/02/24 07:05:52 1.7
+++ cluster/fence/man/fence_node.8 2007/08/22 14:21:14 1.7.2.1
@@ -1,5 +1,5 @@
.\" Copyright (C) Sistina Software, Inc. 1997-2003 All rights reserved.
-.\" Copyright (C) 2004 Red Hat, Inc. All rights reserved.
+.\" Copyright (C) 2004-2007 Red Hat, Inc. All rights reserved.
.\"
.\" This copyrighted material is made available to anyone wishing to use,
.\" modify, copy, or redistribute it subject to the terms and conditions
@@ -16,11 +16,9 @@
[\fIOPTION\fR]...
.SH DESCRIPTION
-\fBfence_node\fP is a program which accumulates all the necessary information
-for I/O fencing a particular node and then performs the fencing action by
-issuing a call to the proper fencing agent. \fBfence_node\fP gets the
-necessary information from the Cluster Configuration System (CCS). CCS must
-be running and properly configured for \fBfence_node\fP to work properly.
+\fBfence_node\fP is a program that reads the fencing settings from
+cluster.conf (through libccs/ccsd) for the given node and then runs the
+configured fencing agent against the node.
.SH OPTIONS
.TP
reply other threads:[~2007-08-22 14:21 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=20070822142114.13975.qmail@sourceware.org \
--to=teigland@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.