| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Local context vs dynamic namespace |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Thu, 15 Apr 2010 08:39:46 +1000 |
| Cc: | pcp <pcp@xxxxxxxxxxx> |
| In-reply-to: | <1271209549.24244.453.camel@xxxxxxxxxxxxxxxx> |
| References: | <378220262.614601271196142712.JavaMail.root@xxxxxxxxxxxxxxxxxx> <1271199338.24244.278.camel@xxxxxxxxxxxxxxxx> <1271209549.24244.453.camel@xxxxxxxxxxxxxxxx> |
| Reply-to: | kenj@xxxxxxxxxxxxxxxx |
On Wed, 2010-04-14 at 11:45 +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. Only caveat to this (now that I've done the work) is the pmcd pmda ... it is excluded from PM_CONTEXT_LOCAL use because it only makes sense when attached to the address space of a running pmcd (not an arbitrary PCP client application). |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates - roll to 3.1.3 and pmcd.conf driving available PMDAs for PM_CONTEXT_LOCAL, Ken McDonell |
|---|---|
| Next by Date: | Re: Local context vs dynamic namespace, Ken McDonell |
| Previous by Thread: | Re: [pcp] Local context vs dynamic namespace, Martin Hicks |
| Next by Thread: | pcp updates - Generalized DSO PMDA support for PM_CONTEXT_LOCAL (part 2), Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |