From: rohara@sourceware.org <rohara@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/fence/init.d fenced
Date: 5 Jan 2007 16:43:20 -0000 [thread overview]
Message-ID: <20070105164320.5369.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: STABLE
Changes by: rohara at sourceware.org 2007-01-05 16:43:20
Modified files:
fence/init.d : fenced
Log message:
Add timeout (default 120 seconds) to 'fence_tool leave'. If the cluster is
not quorate, fenced (fence_tool actually) will wait 120 seconds before it
gives up.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/init.d/fenced.diff?cvsroot=cluster&only_with_tag=STABLE&r1=1.1.2.2.4.1.2.2&r2=1.1.2.2.4.1.2.3
--- cluster/fence/init.d/Attic/fenced 2006/01/23 19:24:10 1.1.2.2.4.1.2.2
+++ cluster/fence/init.d/Attic/fenced 2007/01/05 16:43:20 1.1.2.2.4.1.2.3
@@ -20,6 +20,13 @@
# wait indefinately for fenced to start.
FENCED_START_TIMEOUT=120
+# FENCED_STOP_TIMEOUT -- amount of time to wait for stopping fenced
+# before giving up. If FENCED_STOP_TIMEOUT is positive, then we will
+# wait FENCED_STOP_TIMEOUT seconds before giving up and failing when
+# fenced does not stop. If FENCED_STOP_TIMEOUT is zero, then
+# wait indefinately for fenced to stop.
+FENCED_STOP_TIMEOUT=120
+
start()
{
echo -n "Starting fence domain:"
@@ -76,9 +83,9 @@
if pidof fenced &> /dev/null
then
- fence_tool leave > /dev/null 2>&1
+ fence_tool -t $FENCED_STOP_TIMEOUT leave > /dev/null 2>&1
rtrn=$?
-
+
if [ $rtrn -eq 0 ]
then
success "shutdown"
next reply other threads:[~2007-01-05 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 16:43 rohara [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-24 20:35 [Cluster-devel] cluster/fence/init.d fenced rmccabe
2007-01-05 16:30 rohara
2006-08-09 20:05 jparsons
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=20070105164320.5369.qmail@sourceware.org \
--to=rohara@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.