All of lore.kernel.org
 help / color / mirror / Atom feed
From: jparsons@sourceware.org <jparsons@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/fence/init.d fenced
Date: 9 Aug 2006 20:05:55 -0000	[thread overview]
Message-ID: <20060809200555.21067.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL4
Changes by:	jparsons at sourceware.org	2006-08-09 20:05:55

Modified files:
	fence/init.d   : fenced 

Log message:
	addresses bz191899

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/init.d/fenced.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.1.2.7&r2=1.1.2.8

--- cluster/fence/init.d/Attic/fenced	2006/01/09 20:36:54	1.1.2.7
+++ cluster/fence/init.d/Attic/fenced	2006/08/09 20:05:54	1.1.2.8
@@ -8,11 +8,6 @@
 # Provides: 
 ### END INIT INFO
 
-. /etc/init.d/functions
-[ -f /etc/sysconfig/cluster ] && . /etc/sysconfig/cluster
-
-LOCK_FILE="/var/lock/subsys/fenced"
-
 # FENCED_START_TIMEOUT -- amount of time to wait for starting fenced
 #     before giving up.  If FENCED_START_TIMEOUT is positive, then we will
 #     wait FENCED_START_TIMEOUT seconds before giving up and failing when
@@ -20,6 +15,12 @@
 #     wait indefinately for fenced to start.
 FENCED_START_TIMEOUT=120
 
+. /etc/init.d/functions
+[ -f /etc/sysconfig/cluster ] && . /etc/sysconfig/cluster
+
+LOCK_FILE="/var/lock/subsys/fenced"
+
+
 start()
 {
 	echo -n "Starting fence domain:"



             reply	other threads:[~2006-08-09 20:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 20:05 jparsons [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-05 16:30 [Cluster-devel] cluster/fence/init.d fenced rohara
2007-01-05 16:43 rohara
2007-08-24 20:35 rmccabe

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=20060809200555.21067.qmail@sourceware.org \
    --to=jparsons@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.