From: Steve Dickson <SteveD@redhat.com>
Subject: Re: [PATCH 0/7] nfsstat: adding -D/--diff-stat to nfsstat
Date: Wed, 01 Aug 2007 15:42:16 -0400
Message-ID: <46B0E218.6090703@RedHat.com>
References: <Pine.BSO.4.64.0707311651120.13370@citi.umich.edu>	<46B074A2.4010909@redhat.com>	<Pine.BSO.4.64.0708011149240.25204@citi.umich.edu>
	<46B0C92C.3020807@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Neil Brown <neilb@suse.de>,
	Andrew Richardson <chardson@umich.edu>, nfs@lists.sourceforge.net,
	Alex Soule <soule@umich.edu>,
	"david m. richter" <richterd@citi.umich.edu>
To: Peter Staubach <staubach@redhat.com>
In-Reply-To: <46B0C92C.3020807@redhat.com>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net


Peter Staubach wrote:
> david m. richter wrote:
>>> david m. richter wrote:
>>>     
>>>> 	Hello, Neil,
>>>>
>>>> 	This set of patches adds -D/--diff-stat to nfsstat.  When this flag is
>>>> used, instead of printing out the current total statistics and exiting,
>>>> nfsstat takes a snapshot of the current statistics and pauses until the user
>>>> types ^C, at which point a second snapshot is taken and only the difference
>>>> between the two is printed; i.e., only the statistics gathered during the
>>>> pause.
>>>>       
>>> Hi.
>>>
>>> Perhaps I am missing something, but is something that we really need
>>> to complicate the nfsstat support with?  Is this not easy enough to
>>> do with already existing tools or some easily written support in sh
>>> or perl or awk or name your favorite administrative scripting language?
>>>
>>>    Thanx...
>>>
>>>       ps
>>>     
>> 	
>> 	hello, peter,
>>
>> 	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.
>>
>> 	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?
> 
> It doesn't seem very complicated to me to store the output from two
> nfsstat commands and then write a small script or whatever to parse
> them and create output with the differences.
> 
> This would address the issues with wanting to be able to measure
> the statistics for a particular duration or for the duration that
> a particular problem runs.  Either would be easy to do.
> 
> Now, if someone was proposing a way to do "nfsstat 5" and make the
> output look useful, then I would be behind that 100%.
In a way we already have that... do 'watch nfsstat -c' I think
you get what your looking for...


steved.

-------------------------------------------------------------------------
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