From: "J. Bruce Fields" <bfields@fieldses.org>
To: "david m. richter" <richterd@citi.umich.edu>
Cc: Neil Brown <neilb@suse.de>, Peter Staubach <staubach@redhat.com>,
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: Wed, 1 Aug 2007 13:41:36 -0400 [thread overview]
Message-ID: <20070801174136.GC13441@fieldses.org> (raw)
In-Reply-To: <Pine.BSO.4.64.0708011333100.25204@citi.umich.edu>
On Wed, Aug 01, 2007 at 01:35:16PM -0400, david m. richter wrote:
> > 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
>
>
> just curious: would you be satisfied if the --since file's ctime
> were used as the beginning of the time interval?
Fine by me, but what were you going to use that for? If you're just
producing a diff, then you don't need to know the length of the time
interval. Did you just want to add a header saying "stats since
hh:mm:ss", or did you want to calculate per-second rates?
--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
next prev parent reply other threads:[~2007-08-01 17: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
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 [this message]
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=20070801174136.GC13441@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 \
--cc=staubach@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.