On Fri, Mar 19, 2004, David M. Fetter wrote:
David and co-worker,
> One of my co-workers told me he found a conflict with rc being called.
> [...]
> I wanted to email this to you to get your take in the event it may be
> something you want to address or perhaps something we're doing wrong
> when calling the script.
>
here is a code snippet that shows typical use of rc from within a
script:
eval `${PREFIX}/etc/rc snmp status`
[ ".$snmp_active" != .yes ] && ${PREFIX}/etc/rc snmp start
By calling the rc executable all the rc internal stuff including rc.func
is kept away from the calling script. The output of "rc status" is
designed to be easily parsable as it only uses var=val constructs. In
fact in can be directly executed by a shell (not limited to bash) to
set the three enable|usable|active variables with only a single call to
rc. That's exactly what the eval does.
--
[EMAIL PROTECTED], Cable & Wireless
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
