On Wed, Apr 14, 2010 at 11:45:49AM +1000, Ken McDonell wrote:
> Just to go in circles once more ... PM_CONTEXT_LOCAL is only ever going
> to work for the (DSO) PMDAs that have been "Install"ed on the local host
> because this is the only way to get the correct PMNS installed as well.
> So I think the using pmcd.conf model would work just fine ... and
> Nathan's right we don't need to extend the pmcd.conf format -- if you
> are a DSO PMDA defined in pmcd.conf then by default you're available via
> PM_CONTEXT_LOCAL, end of story.
I've read all of this and I think I understand the proposal. It sounds
pretty good to me. I like that we're using pmcd.conf rather than
inventing a whole new config mechanism.
I intend to review Ken's current iteration of the PM_CONTEXT_LOCAL patch
PS my repetitive strain wrist injury is pretty bad, so I'm limiting
typing time pretty severely these days. This is the major reason why
I haven't been participating much lately.
> On Wed, 2010-04-14 at 08:55 +1000, Ken McDonell wrote:
> > ...
> > 6. With all of this, it is not clear how useful the CLEAR operation to
> > __pmLocalPMDA will be ... I can still see a remote case for needing ADD
> > and DEL, but in some ways the need for all of __pmLocalPMDA and
> > __pmSpecLocalPMDA would almost go away if the PMDAs for PM_CONTEXT_LOCAL
> > was driven off pmcd.conf ... except for your original requirement 8^(>
> > to be able to use metrics from a PMDA when pmcd was not running ... if
> > pmcd is not running then perhaps the PMDAs have not been Installed and
> > pmcd.conf contains no reference to the PMDAs of interest.
> > I think I've argued around a full circle so, probably scrap 5. and 6.
> > and go with the rest of the suggestion.
> pcp mailing list