cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: mgrac@sourceware.org <mgrac@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/rgmanager/src/resources/utils config-u ...
Date: 26 Sep 2006 23:12:39 -0000	[thread overview]
Message-ID: <20060926231239.7146.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	mgrac at sourceware.org	2006-09-26 23:12:39

Modified files:
	rgmanager/src/resources/utils: config-utils.sh messages.sh 

Log message:
	Adds new function (generate_name_for_pid_dir()). Minor update of messages texts.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/src/resources/utils/config-utils.sh.diff?cvsroot=cluster&r1=1.2&r2=1.3
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/src/resources/utils/messages.sh.diff?cvsroot=cluster&r1=1.1&r2=1.2

--- cluster/rgmanager/src/resources/utils/config-utils.sh	2006/09/18 13:48:07	1.2
+++ cluster/rgmanager/src/resources/utils/config-utils.sh	2006/09/26 23:12:38	1.3
@@ -30,13 +30,11 @@
 #
 # "$1" was created from the "$2"
 #
-# This template configuration was automatically generated, and will
-# be automatically regenerated if removed. Please modify this file to
-# speficy subdirectories and/or client access permissions.
-#
-# Once this file has been altered, automatic re-generation will stop.
-# Remember to copy this file to all other cluster members after making
-# changes, or your service will not operate correctly.
+# This template configuration was automatically generated, and will be
+# automatically regenerated if removed. Once this file has been altered,
+# automatic re-generation will stop. Remember to copy this file to all 
+# other cluster members after making changes, or your service will not 
+# operate correctly.
 #
 EOT
 }
@@ -227,6 +225,16 @@
 	return 0;
 }
 
+generate_name_for_pid_dir()
+{
+	declare filename=$(basename $0)
+	
+	echo "$RA_COMMON_pid_dir/$(basename $0 | sed 's/^\(.*\)\..*/\1/')/$OCF_RESOURCE_INSTANCE"
+	
+	return 0;
+}
+
+
 create_pid_directory()
 {
 	declare program_name="$(basename $0 | sed 's/^\(.*\)\..*/\1/')"
--- cluster/rgmanager/src/resources/utils/messages.sh	2006/08/31 13:52:21	1.1
+++ cluster/rgmanager/src/resources/utils/messages.sh	2006/09/26 23:12:38	1.2
@@ -110,7 +110,7 @@
 {
 	case $1 in
 		$CLOG_INIT)
-			ocf_log info "Verifying Configuration Of $OCF_RESOURCE_INSTANCE"
+			ocf_log debug "Verifying Configuration Of $OCF_RESOURCE_INSTANCE"
 			;;
 		$CLOG_SUCCEED)
 			ocf_log debug "Verifying Configuration Of $OCF_RESOURCE_INSTANCE > Succeed"



             reply	other threads:[~2006-09-26 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 23:12 mgrac [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-10 14:10 [Cluster-devel] cluster/rgmanager/src/resources/utils config-u mgrac
2007-01-29 17:27 lhh

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=20060926231239.7146.qmail@sourceware.org \
    --to=mgrac@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).