From: Martin Steigerwald <ms@teamix.de>
To: fio@vger.kernel.org
Cc: Mark Nelson <mnelson@redhat.com>,
Ben England <bengland@redhat.com>, Jens Axboe <axboe@kernel.dk>
Subject: fiologparser.py
Date: Tue, 24 May 2016 12:35:54 +0200 [thread overview]
Message-ID: <12634496.Be1YEipj88@merkaba> (raw)
Hello Mark, Ben,
I found fiologparser.py in fio 2.10 and for now packaged it into the /usr/
share/doc/fio. Yet I´d like to more promintly place it in /usr/bin or so… for
that I would need it to have no script name ending (as according to Debian
Policy). Would be fine with having it renamed to just fiologparser? I can
provide a patch to Jens.
Also it has no manpage, but a short intro in the script source itself. Do you
intent to provide a manpage? Otherwise I may have a go at it with help2man or
so once in a while. It appears to have quite some options:
# ./fiologparser.py
usage: fiologparser.py [-h] [-i INTERVAL] [-d DIVISOR] [-f] [-A] [-a] [-s]
FILE [FILE ...]
fiologparser.py: error: too few arguments
Care to elaborate what these are doing (besides what is mentioned in script
header)?
It requires python-scipy it seems. Anything else?
Thank you,
next reply other threads:[~2016-05-24 10:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 10:35 Martin Steigerwald [this message]
2016-05-24 11:12 ` fiologparser.py Ben England
2016-05-24 14:04 ` fiologparser.py Mark Nelson
2016-05-24 14:11 ` fiologparser.py Jens Axboe
2016-05-24 14:17 ` fiologparser.py Mark Nelson
2016-05-24 15:22 ` fiologparser.py Ben England
2016-05-24 15:28 ` fiologparser.py Jens Axboe
2016-05-24 15:35 ` fiologparser.py Ben England
2016-05-24 16:20 ` fiologparser.py Mark Nelson
2016-05-24 18:38 ` fiologparser.py Jeff Furlong
2016-05-24 20:47 ` fiologparser.py Ben England
2016-05-25 2:04 ` fiologparser.py Mark Nelson
2016-05-25 8:58 ` fiologparser.py Martin Steigerwald
2016-05-25 7:20 ` fiologparser.py Martin Steigerwald
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=12634496.Be1YEipj88@merkaba \
--to=ms@teamix.de \
--cc=axboe@kernel.dk \
--cc=bengland@redhat.com \
--cc=fio@vger.kernel.org \
--cc=mnelson@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.