summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJens Axboe <axboe@suse.de>2005-09-28 17:50:56 +0200
committerJens Axboe <axboe@suse.de>2005-09-28 17:50:56 +0200
commit54aa4b1c9f410181a01996a7288056a58b456d1f (patch)
tree5b7acd23c5c687d5759670117e62d486d11b28cc /README
parent42a58cd1b3940ca1c70619f8af8009273c545b3c (diff)
downloadblktrace-54aa4b1c9f410181a01996a7288056a58b456d1f.tar.gz
blktrace-54aa4b1c9f410181a01996a7288056a58b456d1f.tar.bz2
[PATCH] Add verify_blkparse description to README
Diffstat (limited to 'README')
-rw-r--r--README7
1 files changed, 7 insertions, 0 deletions
diff --git a/README b/README
index 7cd2ba5..ffbe0d7 100644
--- a/README
+++ b/README
@@ -111,6 +111,13 @@ $ blkparse -i <input> [ -o <output> ] [ -b rb_batch ] [ -s ] [ -t ] [ -q ]
-v Print program version info.
+$ verify_blkparse filename
+
+ Verifies an output file from blkparse. All it does is check if
+ the events in the file are correctly time ordered. If an entry
+ is found that isn't ordered, it's dumped to stdout.
+
+
If you want to do live tracing, you can pipe the data between blktrace
and blkparse: