Hello,
Please find answers below.
John.Plocher >>
<===snip====>
In particular, the phrase ...
.... skip fields in the order right to left. On the omission of
fields in random order, the alignment of the header is not
guaranteed.
... sounds like you are defining a "skip list", but later it seems
you aren't. It also seems to say that there is no way to change the
order of displayed fields. The comment about not guaranteeing header
alignment also bothers me - it sounds more like a bug, and not an
architectural requirement.
I would have expected -o to follow the ps convention of defining
a list of fields to display, and then displaying them (and their
headers) in that order:
<===snip====>
** The fields can be omitted in any order.
For example, if fields are passed to "-o" in random order,
1.
vmstat -o memory,kthr 1 3
memory kthr
swap free r b w
46287720 10349200 15 0 0
46321024 10735632 0 0 0
46321016 10735688 0 0 0
field values look scattered
2.
vmstat -o memory,kthr -h 1 3
memory kthr
swap free r b w
44.1G 9.9G 15 0 0
44.2G 10.2G 0 0 0
44.2G 10.2G 0 0 0
Better with "h" option.
3.
vmstat -o kthr,memory 1 2
kthr memory
r b w swap free
15 0 0 46287720 10349248
0 0 0 46318696 10724752
For omission of fields in order, output appears
in the same form as is appearing now.
4.
vmstat -o kthr,memory -h 1 2
kthr memory
r b w swap free
15 0 0 44.1G 9.9G
0 0 0 44.2G 10.2G
User can still obtain values with "-o" option as he does with ps(1).
Probably skip list need not be defined at all.
The order of omission of fields can be left to the user.
This may avoid confusion over the skip list.
Best Regards,
manjula
