I think the "columnspec" flexibility is a wonderful feature...
However... when the taper metrics for data throughput start reaching
4-5 digits on the left side of the decimal point, the time strings in
the same category (TAPER STATS) run into most significant digits of
the throughput data...
Here is an example:
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS
KB/s MMM:SS KB/s
---------------------------------
--------------------------------------- ------------
redbelly /net/redbelly/home1 0 617320 258752 41.9
1:302883.3 0:495294.9
redbelly /net/redbelly/lanl1 0 30 64 213.3 0:00
0.0 0:005461.2
redbelly /net/redbelly/lbnl1 1 6650 736 11.1 0:53
12.7 0:0018841.4
ringneck /net/ringneck/camb1 0 20 64 320.0 0:00
0.0 0:009362.2
ringneck /net/ringneck/tamu1 0 30 64 213.3 0:00
59.1 0:09 7.2
|<================================ widen window to here
================================>|
I intend on looking at the code for columnspec, however I am in the
process of implementing a changer script for my environment... so
formatting will have to take a lower priority...
Primarily I wanted to document this behavior on the list...
thx...
