To get all my server side 'ext' scripts to work consistently, all I did was copy bbdef.sh and bbsys.sh to Hobbit and added the same few lines to each 'ext' script. Something like:

if [ -f $MY_BBDEF ]; then . $MY_BBDEF else echo "Need $MY_BBDEF to run!" exit 1 fi

I made a few edits to bbdef.sh and bbdef.sh calls bbsys.sh, problem solved. Took about 5 minutes. bbsys.sh has all those binaries you are looking for.

~David

Craig Cook wrote:

I'd like to throw in a vote for platform specific definitions as well.

As the maintainer of over 40 scripts, it is a nice feature in BB to allow me to rely on pre defined variables so I don't need to work out which grep I need to use, and be fairly confident a variable will be available.

Personally, I don't like to rely on what my path will return, it is challenging to keep path statements consistent. For security reasons, I always call binaries with the full path if I can.
(Some systems may have /usr/local/bin first, others don't).

I'm okay with hobbit not defining $GREP and friends out of the box, but the ability to do it for each platform would be very nice.

I've been bitten by the stupid default binaries on Solaris as well. Some of us do not have the ability to easily add software to systems (company policies, change control, laws, etc).

Most of my shell scripts check for pre defined variables, if not set, it defines what it thinks it should use and posts a yellow warning complaining about it.

One of the great features of hobbit is the ability to use any BB deadcat script...

I agree this is mainly a client side issue, but something to keep in mind... ;)

Craig

ps. I agree with the knowledge thought, it looks like hobbit will attract some talented followers!

Big Brother Consulting and Training Services www.cookitservices.com

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk