public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: "Fabio M. Di Nitto" <fabbione@fedoraproject.org>
To: cluster-cvs-relay@redhat.com
Subject: fence-agents: master - fence: drop obsoleted fence_manual man page
Date: Mon, 04 May 2009 11:16:00 -0000	[thread overview]
Message-ID: <20090504111536.86E8A1201D4@lists.fedorahosted.org> (raw)

Gitweb:        http://git.fedorahosted.org/git/fence-agents.git?p=fence-agents.git;a=commitdiff;h=9d5a2ef0a38bfbd7dac8b8e1f98a8a2428432c7e
Commit:        9d5a2ef0a38bfbd7dac8b8e1f98a8a2428432c7e
Parent:        58f8fa463ead57a2aa4b646e68e36ac24b20af1b
Author:        Fabio M. Di Nitto <fdinitto@redhat.com>
AuthorDate:    Mon May 4 13:15:14 2009 +0200
Committer:     Fabio M. Di Nitto <fdinitto@redhat.com>
CommitterDate: Mon May 4 13:15:14 2009 +0200

fence: drop obsoleted fence_manual man page

BZ #456505

Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
---
 fence/man/Makefile       |    1 -
 fence/man/fence_manual.8 |   49 ----------------------------------------------
 2 files changed, 0 insertions(+), 50 deletions(-)

diff --git a/fence/man/Makefile b/fence/man/Makefile
index a2f1dec..4f52854 100644
--- a/fence/man/Makefile
+++ b/fence/man/Makefile
@@ -17,7 +17,6 @@ TARGET=	fence_ack_manual.8 \
 	fence_intelmodular.8 \
 	fence_ipmilan.8 \
 	fence_ldom.8 \
-	fence_manual.8 \
 	fence_mcdata.8 \
 	fence_rackswitch.8 \
 	fence_rib.8 \
diff --git a/fence/man/fence_manual.8 b/fence/man/fence_manual.8
deleted file mode 100644
index 018ec0d..0000000
--- a/fence/man/fence_manual.8
+++ /dev/null
@@ -1,49 +0,0 @@
-.TH fence_manual 8
-
-.SH NAME
-fence_manual - program run by fenced as a part of manual I/O Fencing
-
-.SH SYNOPSIS
-.B
-fence_manual
-[\fIOPTION\fR]...
-
-.SH DESCRIPTION
-fence_manual is run by fenced.  It creates a fifo and waits for 
-its counter-part fence_ack_manual(8) to acknowledge that a failed node
-has been reset.  fence_ack_manual(8) should only be run after the operator
-has reset the faulty node.  While waiting for the manual acknowledgement,
-fence_manual also watches for the faulty node to rejoin the cluster;
-if it does, it's taken as an acknowledgement and completes.
-
-Note:  fence_manual is provided for use during testing and evaluation
-only.  Sites should not use fence_manual as the primary fencing method
-on a production cluster.
-
-.SH OPTIONS
-.TP
-\fB-h\fP
-Print out a help message describing available options, then exit.
-.TP
-\fB-q\fP
-quiet mode, no output.
-.TP
-\fB-n\fP \fInodename\fP
-The node name (usually hostname) of the machine that needs to be reset or disconnected from shared storage.
-.TP
-\fB-V\fP
-Print out a version message, then exit.
-
-.SH STDIN PARAMETERS
-.TP
-\fIagent = < param >\fR
-This option is used by fence_node(8) and is ignored by fence_manual.
-.TP
-\fInodename = < param >\fR
-The node name (usually hostname) of the machine that needs to be reset or disconnected from storage.
-.TP
-\fIipaddr = < param >\fR
-IP address or hostname of the machine that needs to be reset or disconnected from storage.  (Deprecated; use nodename instead.)
-
-.SH SEE ALSO
-fence(8), fence_node(8), fence_ack_manual(8)


                 reply	other threads:[~2009-05-04 11:16 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=20090504111536.86E8A1201D4@lists.fedorahosted.org \
    --to=fabbione@fedoraproject.org \
    --cc=cluster-cvs-relay@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).