From: Eric Sandeen <sandeen@redhat.com>
To: linux-btrace@vger.kernel.org
Subject: [PATCH] blktrace: document -k option
Date: Thu, 09 May 2013 02:00:53 +0000 [thread overview]
Message-ID: <518B0355.3030905@redhat.com> (raw)
The -k option was missing from the usage() output and was present
only in the man page synopsis. Say a few more words about it.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/blktrace.c b/blktrace.c
index 89aaaac..4e96573 100644
--- a/blktrace.c
+++ b/blktrace.c
@@ -450,6 +450,7 @@ static char usage_str[] = "\n\n" \
"[ -p <port number> | --port=<port number>]\n" \
"[ -s | --no-sendfile]\n" \
"[ -I <devs file> | --input-devs=<devs file>]\n" \
+ "[ -k | --kill]\n" \
"[ -v <version> | --version]\n" \
"[ -V <version> | --version]\n" \
@@ -467,6 +468,7 @@ static char usage_str[] = "\n\n" \
"\t-p Network port to use (default 8462)\n" \
"\t-s Make the network client NOT use sendfile() to transfer data\n" \
"\t-I Add devices found in <devs file>\n" \
+ "\t-k Kill a running trace\n" \
"\t-v Print program version info\n" \
"\t-V Print program version info\n\n";
diff --git a/doc/blktrace.8 b/doc/blktrace.8
index b5e69b7..7f13231 100644
--- a/doc/blktrace.8
+++ b/doc/blktrace.8
@@ -163,6 +163,13 @@ This only works when supplying a single device, or when piping the output
via "-o -" with multiple devices.
.RE
+\-k
+.br
+\-\-kill
+.RS
+Kill a running trace if blktrace dies
+.RE
+
\-r \fIrel-path\fR
.br
\-\-relay=\fIrel-path\fR
next reply other threads:[~2013-05-09 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 2:00 Eric Sandeen [this message]
2013-05-09 14:00 ` [PATCH] blktrace: document -k option Jeff Moyer
2013-05-09 18:38 ` Eric Sandeen
2013-05-22 7:51 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2013-05-09 1:33 Eric Sandeen
2013-05-09 1:59 ` Eric Sandeen
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=518B0355.3030905@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrace@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 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.