From: Lans Carstensen <Lans.Carstensen-hCDZnVt6e3JSwrhanM7KvQ@public.gmane.org>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/4] nfs-utils: nfs-iostat.py autofs cleanup and option to sort by ops/s
Date: Mon, 14 Sep 2009 21:57:30 -0700 [thread overview]
Message-ID: <4AAF1EBA.4090207@dreamworks.com> (raw)
Here's the testest/reworked patchset for nfs-iostat.py, separating out:
* python path change for package dependency detection and LSB compliance
* Updating list of mount points each interval for autofs environments
* Introduce optparse and update usage/help to use it
* Adding --sort and --list=n options
Thanks in advance for reviewing this.
-- Lans Carstensen, Systems Engineering, Dreamworks Animation
Because they consistently observe and listen, the humble improve.
-- Wynton Marsalis
next reply other threads:[~2009-09-15 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 4:57 Lans Carstensen [this message]
[not found] ` <4AAF1EBA.4090207-hCDZnVt6e3JSwrhanM7KvQ@public.gmane.org>
2009-09-15 18:49 ` [PATCH 0/4] nfs-utils: nfs-iostat.py autofs cleanup and option to sort by ops/s Steve Dickson
-- strict thread matches above, loose matches on Subject: below --
2009-08-26 4:59 Lans Carstensen
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=4AAF1EBA.4090207@dreamworks.com \
--to=lans.carstensen-hcdznvt6e3jswrhanm7kvq@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/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