pcp
[Top] [All Lists]

Re: [pcp] Simple fix needed, not docs? (was Re: RFC2: fetchgroup api)

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] Simple fix needed, not docs? (was Re: RFC2: fetchgroup api)
From: Marko Myllynen <myllynen@xxxxxxxxxx>
Date: Mon, 7 Dec 2015 09:03:48 +0200
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <447344479.34949675.1449195913043.JavaMail.zimbra@xxxxxxxxxx>
Organization: Red Hat
References: <20151201145903.GB31003@xxxxxxxxxx> <1224565686.32458903.1449038493129.JavaMail.zimbra@xxxxxxxxxx> <20151203001437.GA2531@xxxxxxxxxx> <37369073.33594680.1449118672756.JavaMail.zimbra@xxxxxxxxxx> <20151203141450.GB2531@xxxxxxxxxx> <447344479.34949675.1449195913043.JavaMail.zimbra@xxxxxxxxxx>
Reply-to: myllynen@xxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
Hi,

On 2015-12-04 04:25, Nathan Scott wrote:
> 
> Case in point - https://bugzilla.redhat.com/show_bug.cgi?id=1287678 -
> your pmstat bug from yesterday.  Took all of 5 minutes to diagnose and
> fix - you could have easily resolved it.

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'",
pmdumptext -g seems to be a no-op? -p works as expected with
pmstat/pmval but does nothing with pmdumptext.

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.

Thanks,

-- 
Marko Myllynen

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