Hi,
On 2015-12-07 22:49, Nathan Scott wrote:
> ----- Original Message -----
>> [...]
>> how is this -g switch supposed to work by the way? I tested the fixed
>> pmstat -g and also pmval -g and pmdumptext -g. pmstat -g / pmval -g give
>> me a pop-up window complaining "pmtime: invalid option -- 'h'",
>
> You'll need a pmtime(1) binary built from git master installed.
thanks, pmval/pmstat -g/-p both work ok then.
>> pmdumptext -g seems to be a no-op? -p works as expected with
>> pmstat/pmval but does nothing with pmdumptext.
>
> OK, I'll check out pmdumptext today, but possibly similar root cause.
Turns out it's been mentioned in the past:
http://www.pcp.io/pipermail/pcp/2009-November/000692.html
>> I was mainly checking whether this would be something to consider in the
>> context of pmrep but honestly I don't see this functionality very
>> useful. Also not sure how much client side coding that would be needed,
>> enabling -g/-p via Python PMAPI didn't seem to be enough.
>
> You need a bit of client side logic, yep - a callback function or two and
> usually special-case handling for gui-mode inside the fetch loop. See pmval
> code around opts.guiflag and the pmTimeControls data structure.
>
> I've found it to be handy in the past for scanning around quickly in large
> archives using pmval - so, yep, could make sense for pmrep.
Hmm, ok, -g is available and would still free up -p for this just in
case we want to do this in the future. I was planning to do one (or two)
cmd line switch renames anyway so perhaps I'll include this as well.
Thanks,
--
Marko Myllynen
|