pcp
[Top] [All Lists]

Re: Local context vs dynamic namespace

To: kenj@xxxxxxxxxxxxxxxx
Subject: Re: Local context vs dynamic namespace
From: nathans@xxxxxxxxxx
Date: Mon, 12 Apr 2010 15:31:29 +1000 (EST)
Cc: pcp <pcp@xxxxxxxxxxx>
In-reply-to: <121784609.558421271050008299.JavaMail.root@xxxxxxxxxxxxxxxxxx>
Sender: nscott@xxxxxxxxxx
----- "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx> wrote:

> This is pretty much outside the scope of what I was aiming for with
> the dynamic metrics, although it is not unreasonable.
> 
> It will mean even more code being copied and changed from pmcd to
> libpcp
> as the current code in the library has no support for making the
> needed DSO calls.
> 
> So it is not a simple change.
> 
> The mmv pmda will sneak in on the back of the default dso table for
> PM_CONTEXT_LOCAL, but how will you get the aconex pmda into the dso
> table (pminfo -L -K 123,aconex/pmda_aconex.so,aconex_init ... in the
> bash stuff)?
> 

Good point.  I'll go with dropping -L in the bash completion, I think.
Guess we could do something like the /etc/ld.so.conf.d/ approach with
local context pmdas, to specify all that should be open when clients
open local contexts, but probably overkill at this stage (but perhaps
thats worth thinking about, instead of putting -K in all the tools?).

Hmmm, probably not a good time to be suggesting that, now that all the
work is done ... :)

cheers.

-- 
Nathan

<Prev in Thread] Current Thread [Next in Thread>