[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bayonne-devel] Re: grep dlgnDriver = dialogic or globalcall?
From: |
Erik Enge |
Subject: |
[Bayonne-devel] Re: grep dlgnDriver = dialogic or globalcall? |
Date: |
Sat, 19 Jul 2003 10:02:17 -0400 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Portable Code, linux) |
David Sugar <address@hidden> writes:
> At the moment, /etc/sysconfig/bayonne is the preferred way to specify
> a driver, with the init script's autodetect used as a default to
> automate driver selection.
I guess you are referring to the following code in sbin/bayonne (the
test for /etc/sysconfig/bayonne appears several times in the file so my
comments would apply to all of them):
if test -f /etc/sysconfig/bayonne ; then
. /etc/sysconfig/bayonne
if test ! -z "$CONFIG" ; then
sysconfig="$CONFIG"
fi
fi
if test ! -z "$BAYONNE_CONFIG" ; then
sysconfig="$BAYONNE_CONFIG"
fi
At the top of that script we have:
sysconfig="/share/sys/bayonne/bayonne-1.2.6-1/etc"
Perhaps we could do something like this instead:
if test -f $sysconfig/bayonne
. $sysconfig/bayonne
fi
And then set $sysconfig to be /etc/sysconfig by default during the
compile process unless --sysconfdir is specified?
I also do not understand the semantics of the two other if-tests for
$CONFIG and $BAYONNE_CONFIG. Why are they here? Do we really need
both? How would they get used?
My issue with the current way is that it does not scale at all for us.
We have multiple Bayonne installations because of the testing routines
we have to go through before we deploy (we do this religiously with all
software) and we need to be able to have them use individual
configuration files.
Now, I know that I can export environment variables and have them
overwrite whatever, if any, /etc/sysconfig/bayonne sets for me but that
seems like a hack and there doesn't seem to be a preferred way of doing
it.
Erik.