Are you familiar with C programming at all? Your question "...is the
hobbitd_sample.c something that I should look at for this?" almost
sounds like you may not be. You could be for a long haul if your intent
is to learn a programming language while converting your existing Hobbit
shell script into something more efficient. It's not going to be a
simple cut-paste-compile scenerio, that's for sure. Pardon me if I've
interpreted you posting incorrectly.
Personally, I use PERL for my Hobbit server scripts, except the ones
that are the simplest-of-the-simple, and for those I do use just plain
inefficent shell. I know C as well, but find PERL to be amost as
efficient for what I do, and a heckuva lot quicker to program in.
From: Gary Baluha [mailto:user-ae3e15c22de1@xymon.invalid]
Sent: Thursday, June 28, 2007 12:13 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] Server-side extension scripts: shell vs. C programming
I remember reading somewhere in the Hobbit documentation that when an
extension script starts to do a lot of things, it should be coded in a
compiled language such as C, instead of as a shell script. I have a
custom script that takes a lot of data and converts it into NCV graphs,
and I believe it is at the point where I should consider rewriting it in
C.
Before I get to far into it, is the hobbitd_sample.c something that I
should look at for this? I'm not sure if I'm reading the documentation
on it correctly, if it is a good example for an external script. Has
anyone else had experience in needing to convert a shell script to
C/C++/etc for Hobbit? I'm just trying to get a rough idea of how much
effort this will require.