Brian Elliott Finley wrote:
Better yet, is there any reason not to source the functions prior to
sourcing the variables?
Some functions in particular for the monitoring stuff are variables.txt
dependent... if you think this could be a problem we can resolve in this
way:
. /tmp/variables.txt
. /etc/init.d/functions
[ ! -e /tmp/variables.txt ] && shellout
Cheers,
-Andrea
-------- Original Message --------
Subject: [Systemimager-commits] r3274 - trunk/etc
Date: Fri, 25 Nov 2005 10:26:30 -0600
From: Andrea Righi <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Author: arighi
Date: 2005-11-25 10:26:29 -0600 (Fri, 25 Nov 2005)
New Revision: 3274
Modified:
trunk/etc/autoinstallscript.template
Log:
load variables first of all, in order to preserve variables definition
inside functions
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
