On Wed 01 Mar 2006 at 06:19PM, Rich Brown wrote:
> It prints the header after every 24(-ish) lines of output. I'm looking
> forward to hearing how this gets used so the output can be polished up.
I think the algorithm should be:
If only printing one line at a time (fsstat ufs 1),
print a header every 10 lines or so.
If printing multiple lines at a time, always print a
header.
> BTW, For easier reading (and date/time correlation) try:
>
> fsstat -T d {interval}
You know that -T is not in the usage message, right?
> >4. I'm not sure that the default output is the one which most admins
> > would want at a glance. Just my $0.0002.
>
> This part was challenging. The idea was to give an overview of what was
> happening on the system. (Separating out the set/get attr ops can be
> useful for NFS server/client observability which is what gave birth to
I think having set/get attr ops available via the -a option is great; I
just think that as an admin I want to spot the big number, and then
drill down from there. If attrs were high, I'd use your
attributes-in-depth option to learn more.
I also won some space by merging the name operations; I think that
new, remove, and name change could all potentially be merged into
'name ops'.
Again, I think the default output is a bit puzzling. There is
the additional question: what does the default output look like
in a zone? If the kstats aren't virtualized per-zone, it starts
to look less and less useful.
-dp
--
Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
