Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "david m. richter" <richterd@citi.umich.edu>
Cc: Neil Brown <neilb@suse.de>,
	Andrew Richardson <chardson@umich.edu>,
	nfs@lists.sourceforge.net, Alex Soule <soule@umich.edu>
Subject: Re: [PATCH 0/7] nfsstat: adding -D/--diff-stat to nfsstat
Date: Tue, 31 Jul 2007 19:41:56 -0400	[thread overview]
Message-ID: <20070731234156.GA18172@fieldses.org> (raw)
In-Reply-To: <Pine.BSO.4.64.0707311928380.5541@citi.umich.edu>

On Tue, Jul 31, 2007 at 07:29:28PM -0400, david m. richter wrote:
> > Sounds useful, though I think it would be even more useful if you
> > could specify a number of seconds rather than needing to interrupt.
> > That way you could use it in a script.
> > Maybe even get it to repeat every n seconds?
> > 
> > Thanks. I'll look through the patches.
> > 
> > NeilBrown
> 
> 	roger -- i'll look at adding an optional timeout w/ optional 
> repeat.  good idea. 

Sure, I agree that it'd be more convenient for scripting.  Alternatively
(or also) we could allow the user to pass in a file with previous
nfsstat output, so you could do something like

	nfsstat >tmp
	sleep 60
	nfsstat --since=tmp

But personally the ctrl-C thing is what I expect to use 99% of the
time, so I'm happy to see that done first.

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

  reply	other threads:[~2007-07-31 23:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 21:38 [PATCH 0/7] nfsstat: adding -D/--diff-stat to nfsstat david m. richter
2007-07-31 22:11 ` Neil Brown
2007-07-31 23:29   ` david m. richter
2007-07-31 23:41     ` J. Bruce Fields [this message]
2007-08-01  0:42     ` Neil Brown
2007-08-01 11:55 ` Peter Staubach
2007-08-01 15:59   ` david m. richter
2007-08-01 16:49     ` Trond Myklebust
2007-08-01 17:07       ` J. Bruce Fields
2007-08-01 17:42         ` david m. richter
2007-08-01 16:50     ` J. Bruce Fields
2007-08-01 17:35       ` david m. richter
2007-08-01 17:41         ` J. Bruce Fields
2007-08-01 17:45           ` david m. richter
2007-08-01 17:46         ` Trond Myklebust
2007-08-01 17:48           ` david m. richter
2007-08-01 18:02             ` Trond Myklebust
2007-08-01 18:12             ` david m. richter
2007-08-01 18:15             ` Muntz, Daniel
2007-08-01 18:37               ` david m. richter
2007-08-01 18:41                 ` Trond Myklebust
2007-08-01 18:47                   ` david m. richter
2007-08-01 18:50                 ` J. Bruce Fields
2007-08-01 20:03                   ` Steve Dickson
2007-08-01 20:48                     ` J. Bruce Fields
2007-08-01 21:50                       ` Steve Dickson
2007-08-01 22:40                       ` Trond Myklebust
2007-08-01 18:38               ` J. Bruce Fields
2007-08-01 17:52           ` J. Bruce Fields
2007-08-01 17:55     ` Peter Staubach
2007-08-01 18:14       ` david m. richter
2007-08-01 18:22         ` Peter Staubach
2007-08-01 18:25           ` david m. richter
2007-08-01 18:57           ` J. Bruce Fields
2007-08-01 19:35           ` Chuck Lever
2007-08-01 20:16             ` Steve Dickson
2007-08-01 20:54               ` Chuck Lever
2007-08-01 19:42       ` Steve Dickson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070731234156.GA18172@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chardson@umich.edu \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=richterd@citi.umich.edu \
    --cc=soule@umich.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox