pcp
[Top] [All Lists]

Re: [pcp] Dumb question about disk.dev.read_bytes

To: Greg Banks <gnb@xxxxxxxxxxx>
Subject: Re: [pcp] Dumb question about disk.dev.read_bytes
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 21 Apr 2010 16:24:24 +1000 (EST)
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
In-reply-to: <4BCE96A2.80004@xxxxxxxxxxx>
----- "Greg Banks" <gnb@xxxxxxxxxxx> wrote:

> nathans@xxxxxxxxxx wrote:
> > ----- "Greg Banks" <gnb@xxxxxxxxxxx> wrote:
> >
> >   
> > What options are you using?  I see this... (Linux)
> >
> > [...]
> > The first function (checkUnits) here...
> >
> http://oss.sgi.com/cgi-bin/gitweb.cgi?p=pcp/pcp-gui.git;a=blob_plain;f=src/dumptext/pmdumptext.cpp;hb=HEAD
> > ...has a comment "// Only scale units if interactive and not raw"
> which
> > looks like the underlying mechanism (the test on the next line).
> >
> >   
> 
> Ah.
> 
> What I was trying to do was output units with full precision and as 
> units that are consistent across platforms, for input into a script 
> which does mathematics on the values.
> 
> After your comments and re-reading the manpage properly I tried using
> 
> -i. Unfortunately I get two things I don't want: reduced precision and
> 
> unit suffixes, e.g. "0.11G" instead of "114184632.76".  I need unit 
> conversion and rate conversion, but no pretty formatting.
> 
> I don't need that "human-readable" stuff from pmdumptext; kmchart does
> a much better job at humanifying the data.

Hmm - well, if there's no way to coerce the current dazzling array of
command line options to giving that, just whack a --gnb option in there
and send a patch (you know where the code is now anyway, from that last
url).

cheers.

-- 
Nathan

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