On 11/25/2009 at 11:12 AM, in message
75fb37ae0911251012i328f8f00u5586dab199c97...@mail.gmail.com, Sylvester Steele
sylvesterste...@gmail.com wrote:
I don't know why you would be getting a segfault on this line. Gmond
expects the array to be NULL terminated so all you are doing is adding one
Ok, so I tried to make a dynamically initializing module. I am
basically trying to convert the example module to a dynamically
initializing one..
My metrc_init function looks like this:
static int ex_metric_init ( apr_pool_t *p )
{
Ganglia_25metric* gmi;
apr_pool_create(pool, p);
On 11/25/2009 at 9:16 AM, in message
75fb37ae0911250816k5e7e0373x25ad2ee613930...@mail.gmail.com, Sylvester Steele
sylvesterste...@gmail.com wrote:
Ok, so I tried to make a dynamically initializing module. I am
basically trying to convert the example module to a dynamically
initializing one..
My guess is because you have static string pointers being passed from a
DSO module to gmond. I would suggest using apr_pstrdup(p, string literal
here) to allocate the memory from an APR memory pool before handing the
pointers back to gmond.
Thanks Brad- that helped, but I am still getting a seg
I don't know why you would be getting a segfault on this line. Gmond expects
the array to be NULL terminated so all you are doing is adding one extra
entry and filling it will NULLs. With the array being NULL terminated, gmond
doesn't have to keep track of the metric count, it only has to
On 11/19/2009 at 6:32 AM, in message
75fb37ae0911190532t17685eb0uc1db8390546b4...@mail.gmail.com, Sylvester Steele
sylvesterste...@gmail.com wrote:
Take a look at the pyth_metric_init() function in the mod_python.c module.
At the end of the function, mod_python takes all of the metric
On 11/19/2009 at 9:13 AM, in message
75fb37ae0911190813q66cf1f96w1afe84f8bdbe1...@mail.gmail.com, Sylvester Steele
sylvesterste...@gmail.com wrote:
I'm not sure what you are looking for. The purpose of the code that I
referred to was to show how a module would generate the metric definitions
Kim,
I got the tarball to which you'd put up the link earlier on in the mailing
list. I got your module to work no problem there!
But, I have a question:
All the Ganglia modules have a metric array. The mod_cpu has this:
static Ganglia_25metric cpu_metric_info[] =
{
{0, cpu_num,1200,
There are more qualified people on this list to answer your question
about dynamically setting metric callbacks.
But a quick glance through gmond.c reveals that it might not be
possible with the current framework.
When gmond starts up, it calls the function setup_metric_callbacks(),
which steps
On 11/16/2009 at 3:04 PM, in message 002c01ca6708$d7770020$866500...@com,
Sylvester Steele sylvesterste...@gmail.com wrote:
Kim,
I got the tarball to which you'd put up the link earlier on in the mailing
list. I got your module to work no problem there!
But, I have a question:
All the
I think you can search for iostat in the archives. If you can't find it,
I'll dig it up and reply again.
Kim,
I did get hold of the tar.gz that you'd put up:
So if I take out your iostat module- put in mine, make appropriate
changes to other files (basically make sure that all my functions
On 11/10/2009 at 8:30 PM, in message
75fb37ae0911101930g55978c94u1a16c48fd5cc2...@mail.gmail.com, Sylvester Steele
sylvesterste...@gmail.com wrote:
-- Forwarded message --
From: Sylvester Steele sylvesterste...@gmail.com
Date: Tue, Nov 10, 2009 at 10:19 PM
Subject: Re:
I've written the iostat standalone DSO module a while back in C. I do
have the whole build process documented (to some degree) and provided
template for creating standalone DSO.
I think you can search for iostat in the archives. If you can't find
it, I'll dig it up and reply again.
On Nov
-- Forwarded message --
From: Sylvester Steele sylvesterste...@gmail.com
Date: Tue, Nov 10, 2009 at 10:19 PM
Subject: Re: [Ganglia-developers] Getting started with developing a
C++ DSO module
To: Brad Nicholes bnicho...@novell.com
1. Compile to .so
2. Place compiled .so in the
14 matches
Mail list logo
