Re: [PATCH 0/7] nfsstat: adding -D/--diff-stat to nfsstat

["J. Bruce Fields" <bfields@fieldses.org>]

On Wed, Aug 01, 2007 at 11:59:45AM -0400, david m. richter wrote:
> 	yes.  :)  right now, there's no easy way to run a test and get 
> stats for just that test, since the counters persist -- so you have to do 
> things like run a test, unmount, remount, etc.  this is a quick way to get 
> stats collected over an arbitrary period.  and it's not very complicated, 
> really.

Yah.  Especially for debugging other peoples' problems over email, it'd
be helpful to have simple one-line commands that use programs that are
installed everywhere by default.  In this case adding on to nfsstat
looks like the simplest way to achieve that.  But a simpler
implementation would be welcome, of course, if you want to have a go at
it.

> 	i don't think a shell/perl/python/etc script would be anywhere as 
> useful a substitute.  and with neil's suggestion about adding an optional 
> timeout to make it easier to use -in- scripts, i think we're on the right 
> track with this approach.
> 
> 	.. thoughts/ideas?

Can I make one more attempt to interest someone in implementing the
--since=baseline-file approach?  It'd be fun, and would make some more
flexible use cases very simple.  You could still get a time interval:

	nfsstat >tmp
	sleep 30
	nfsstat --since=tmp

or you could do other stuff:

	nfsstat >tmp
	run-my-weird-test-case-here
	nfsstat --since=tmp

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs