> The first is the "h" option which will produce output in > human readable format, thereby making it easily readable > to the user, > > Example "h" option output: > > vmstat > kthr memory page disk faults cpu > r b w swap free re mf pi po fr de sr f0 m0 m1 m2 in sy cs us sy id > 2 0 0 4460632 531268 333 4575 140 51 50 0 20 -0 0 5 3 1927 4463 528 22 13 65 > > vmstat -h > kthr memory page disk faults cpu > r b w swap free re mf pi po fr de sr f0 m0 m1 m2 in sy cs us sy id > 2 0 0 4.3G 518.8M 332 5K 140K 51K 50K 0 20 -0 0 5 3 1927 4462 528 22 13 65
I certainly don't find that any more readable. The units are confusing too. For pageins, is that pages, kilobytes, or k/s? Why aren't the cpu fields "humanized"? > The fields that are allowed for the "o" > option are: > kthr, memory, page, faults, cpu ... > vmstat -po memory,page,executable 2 2 OK, so what fields are allowed for the -o option? I didn't see 'executable' listed. The -o option is good, as it allows you to make the display more readable by removing irrelevant fields that just add cluttter (the disk columns are rarely useful). It would be better if selecting fewer columns spread the display out so the columns lined up, which would make it far more readable. I'm not convinced that the -h is a good idea, though. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
