pcp
[Top] [All Lists]

Local context vs dynamic namespace

To: kenj <kenj@xxxxxxxxxxxxxxxx>
Subject: Local context vs dynamic namespace
From: nathans@xxxxxxxxxx
Date: Mon, 12 Apr 2010 11:56:50 +1000 (EST)
Cc: pcp <pcp@xxxxxxxxxxx>
In-reply-to: <1688696220.546661271036941381.JavaMail.root@xxxxxxxxxxxxxxxxxx>
Sender: nscott@xxxxxxxxxx
Hi Ken,

We're a long way down the path of converting all of our production
environment over to using MMV and the dynamic namespace extensions.
All going swimmingly so far.  Just this morning we came across an
issue with the bash metric name auto-completion.  This uses pminfo
in local context mode (-L) to provide a list of metric names which
the shell can use for name completion with several pcp commands.

In our namespace we have MMV:*:* (a top level mmv namespace entry)
and ACONEX:*:* as well (likewise, at the top level).  In local mode
pminfo does not traverse, just reports "mmv" and "aconex".

We can change the bash code to not use -L, but that seems like its
just avoiding the real problem - should local context mode be able
to descend into these parts of the namespace?  I woulda thought it
should, just like regular pmcd mode...?

cheers.

-- 
Nathan

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