[hobbit] Nagios client, Hobbit server anyone?

[Ward, Martin]

>>I took a look at the weekend but came up against a wall trying to 
>>extract the relevant code from  bbproxy. I think the issue I was
having 
>>was that bbproxy is heavily written to merge multiple packets from
>> the client (combining) and send them on to the Hobbit server in one
go.
>>I just needed something that told
>> me what the format of a bbproxy data packet looked like and how to
send
>>it to the main server.
>
>I wouldn't mix bbproxy into this at all. Write a simpler tool to run
the
>Nagios plugin, extract the relevant data from the output, 
and generate Hobbit-style status-messages. Then send these the usual way
>(either invoke the "bb" utility to do it, or if you link your program
with
>the "libbbgen.a" library from Hobbit, then you can use Hobbit's
"sendmessage()"
>routine.

Sorry Henrik, I didn't explain myself very well (or at all for that
matter!).

I was looking at bbproxy's source to get some idea of how to proxy a
message from
 one machine through another to the Hobbit server, the original
intention being to
 strip your bbproxy code of everything that I didn't need and use what's
left (with
 acknowledgements to you as the original author). However having looked
at the
 bbproxy code I agree with you that doing so would be more difficult
than actually
 writing the whole program myself.

Instead I will look at Hobbit's sendmessage() routine as you suggest and
see if I can
 use that instead. It's really just the format of the packet when it
contains proxied
 data that I need to understand.

|\/|artin


*************************************************************************************
The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. 

The contents of this message and its attachments are confidential and may also be subject to legal privilege.  If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security at colt.net and delete the message and any attachments without retaining any copies. 

Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. 

No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party.  

Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.