Cool! Thanks for the tip.
I was a bit naive in thinking hobbitlaunch might just pass ENVFILE and
LOGFILE to CMD as env variables. I had just reviewed hobbitlaunch.c and
environ.c and found that hobbitlaunch redirects stdout/stderr to LOGFILE
before calling CMD. And also the ENVFILE processing is a little more
complex due to the AREA stuff (which implies hobbitclient.cfg is not a
sourceable env file, as it almost appears to be in it's default state).
I'll look at bbcmd. I was going to hack my own way through this, but if
there's already an existing path, I'm all for the easy way!
Thanks
-----Original Message-----
From: Stef Coene [mailto:user-dbffe946c0f4@xymon.invalid]
Sent: Saturday, June 23, 2007 11:55 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] hobbitfetch replacement with ssh
On Saturday 23 June 2007, Haertig, David F (Dave) wrote:
Good idea! I just need to see how hobbitlaunch normally passes
ENVFILE and LOGFILE to CMD (hobbit-client.sh) when it normally envokes
CMD. So I can do that when I invoke hobbit-cient.sh manually via ssh.
Probably just as simple env variables. I'll check the source code for
hobbitlaunch, or just "guess-and-test".
You can use bbcmd. So "bbcmd hobbitclient.sh". bbcmd will set the
needed environment variabels. You probably have to specify the full
path to hobbitclient.sh.
Stef