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".
BTW, the clients appear to NOT attempt to connect to Hobbit server, and still behave gracefully, if you set BBDISP=0.0.0.0 and BBDISPLAYS="". At least the logfile quits complaining about that "Whoops!" message. And the msx.XXX.txt file is still generated normally. Great!
One last thing is to figure out why there aren't the normal "Client data available" links on the Hobbit webpages (not a show-stopper if they aren't there).
Thanks
-----Original Message----- From: Stef Coene [mailto:stef.coene at docum.org] Sent: Saturday, June 23, 2007 6:42 AM To: hobbit at hswn.dk Subject: Re: [hobbit] hobbitfetch replacement with ssh
On Saturday 23 June 2007, Haertig, David F (Dave) wrote:
And I also need to investigate the possible problems of having the client script and the server script run asynchronously. It may be possible to upload the same msg.XXX.txt file twice in a row if timings/delays fall just right. I need to see how that would affect the RRD/graphing part of Hobbit. It might confuse the heck out of it. Why not ssh to the client, execute hobbit-client.sh and pick up the resulting file ?
Stef
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk