pcp
[Top] [All Lists]

Re: [question] PCP UI FrontEnd

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [question] PCP UI FrontEnd
From: fche@xxxxxxxxxx (Frank Ch. Eigler)
Date: Tue, 13 Oct 2015 15:35:26 -0400
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20150729230247.GN6728@xxxxxxxxxx> (Frank Ch. Eigler's message of "Wed, 29 Jul 2015 19:02:47 -0400")
References: <f8fde1169e264460bc2e250d2c9d7df0@xxxxxxxxxxxxxxxxxxxxxxxxx> <y0m1tft2sqt.fsf@xxxxxxxx> <55B6B46E.2050306@xxxxxxxxxxxxxxxx> <y0m4mkpyu9j.fsf@xxxxxxxx> <55B70B48.7060704@xxxxxxxxxxxxxxxx> <20150729230247.GN6728@xxxxxxxxxx>
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
Hi, Ken -

Sorry to reincarnate this necrothread [1], but I'm looking for
definitive advice re. dynamic configuration for pmlogger.

[1] http://oss.sgi.com/pipermail/pcp/2015-July/007884.html


> [...]
>> I'm afraid I don't know what "the desired automation" would look like 
>> ... could you sketch out some meta syntax that you've got in mind?
>
> Sure.  One way is a straight insertion of the pmie expression
> language:
> [...]
> This assumes that pmie core could be reworked to allow its reuse
> pmlogger.  If not, then reinvent the wheel starting simple, and work
> up.  For example:
> [...]

I'd like to find out whether there's any sympathy to these types of
extensions in pmlogger (effectively a sort of a unification with
pmie).  If not, is there any opposition to having a new pcp pmlogger
type tool that does include these sorts of extensions?


- FChE

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [question] PCP UI FrontEnd, Frank Ch. Eigler <=