On Wed, 2006-03-01 at 23:06, Rich Brown wrote: > Hi Peter, > > Good idea about the class name. I'll look into it.
Thanks! It would make life much easier - pick all fsstat kstats by filtering on the class name, and equally being able to identify it as an fsstat kstat just by looking at the class name. And a quick look at the source indicates that it should be rather straightforward. > I'm curious to know what you would use the raw kstat information > for. We're always looking for ideas on how to the system more > observable in a way that's useful for customers. To write tools that present the information in ways that the standard tools don't. Ideally without running the output from a standard tool through a complex awk script... For example, I'm working on a graphical (ie. java jni) interface to kstats. Here I want the raw kstats, and want to be able to display them and drill down into them interactively. (And, with luck, use the new dtrace java binding to be able to drill further down to the cause.) I've already written jiostat; I detect a jfsstat in the works. -- -Peter Tribble L.I.S., University of Hertfordshire - http://www.herts.ac.uk/ http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
