Hi Chandana,
----- Original Message -----
> Hello Nathan,
>
> Thank you very much for your help. I got the new metrics working. The
> reason it did not work last evening was that the data returned from
> 'show slave status' is a single row, not a bunch of rows.
>
Aha!
> I have now added all the slave status metrics in, hope I have got the
> semantics right. I would appreciate if you (or someone) can cast an
> eye over them.
>
Will take a look today.
> I need to get these metrics into my environment as soon as possible.
> I
> would like to generate a new pcp rpm with the new code. How should I
> name the rpm to ensure that the change goes in cleanly when I upgrade
> ?.
> The current RPM is pcp-3.6.9-1. If the next RPM is going to be
> pcp-3.6.10-1, then I can safely use pcp-3.6.9.1-1. Is that ok ?
I'd usually would go for something like "pcp-3.6.9-1chandana" or
"...-1git" or something like that. But, looks like 4-part version
numbers are supported by rpm, and we're unlikely to ever release a
PCP conflicting with that, so your convention should work fine too.
cheers.
--
Nathan
|