On Mon, Jun 15, 2015 at 10:36:12AM -0600, Warner Losh wrote:
>
> > On Jun 14, 2015, at 12:53 PM, Adrian Chadd <adr...@freebsd.org> wrote:
> >
> > I do like how zero percent of the comments are "hey, maybe we need
> > unit tests that run these tools and ensure they output the right
> > stuff." If this were ${WORK} and I were ${BOSS}, I'd have asked the
> > libxo developers to include unit tests before/after for each thing
> > they broke, so we don't have a repeat of this kind of thing. But, this
> > apparently isn't ${WORK} and I definitely don't want to be anyones
> > boss, so..
>
> gstat still produces the right output. It simply has been broken in that
> you can't just hit 'q' anymore. So while necessary, it wouldn't be
> sufficient.
I am about initial gstat behavior: you can't be do `gstat >
output_log`, wait hour, press ^C and analyse output -- gstat exit
after one ineration. I am talk all utilites have different behavior --
some exits by pressing 'q', some only by ^C (systat), some can be infinitly
output to file|pipe, some -- not. Some have looped mode, some -- not,
some can handle multiple obejcts (gstat, iostat), some -- not (netstat
-nbI).
And more: ix show network statics in netmap mode, igb -- don't show.
No unification. This is more vital, I think.
And no tools for collect correlation data -- for example collect at
same time CPU load by core, i/o load by disk and network load by
inetrface. You may talk about Graphite, but graffit is crap:
http://grisha.org/blog/2015/05/04/recording-time-series/
_______________________________________________
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
