summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJens Axboe <axboe@suse.de>2006-02-15 09:33:45 +0100
committerJens Axboe <axboe@suse.de>2006-02-15 09:33:45 +0100
commitf531b94dbe7948e479a6cfa838cda9fb3c321f0c (patch)
tree658782045de0b9c474717b28986f9957d52919ea /README
parentb444507cc5cfae28347b45ea73a2e8bb4845f760 (diff)
downloadblktrace-f531b94dbe7948e479a6cfa838cda9fb3c321f0c.tar.gz
blktrace-f531b94dbe7948e479a6cfa838cda9fb3c321f0c.tar.bz2
[PATCH] blktrace/README: update to include description of new net parameters
Diffstat (limited to 'README')
-rw-r--r--README17
1 files changed, 12 insertions, 5 deletions
diff --git a/README b/README
index 5f79e36..7236966 100644
--- a/README
+++ b/README
@@ -60,6 +60,10 @@ $ blktrace -d <dev> [ -r relay_path ] [ -o output ] [ -k ] [ -w time ]
-b Sub buffer size in KiB.
-n Number of sub buffers.
+ -l Run in network listen mode (blktrace server)
+ -h Run in network client mode, connecting to the given host
+ -p Network port to use (default 8462)
+ -s Make the network client use sendfile() to transfer data
-V Print program version info.
$ blkparse -i <input> [ -o <output> ] [ -b rb_batch ] [ -s ] [ -t ] [ -q ]
@@ -142,13 +146,16 @@ and blkparse:
This has a small risk of displaying some traces a little out of sync, since
it will do batch sorts of input events. Similarly, you can do traces over
-the network with eg netcat:
+the network. The network 'server' must run:
-% blktrace -d /dev/sda -o - | netcat parsehost portno
-% netcat -l -p portno tracehost | blkparse -i -
+% blktrace -l
+
+to listen to incoming blktrace connections, while the client should use
+
+% blktrace -d /dev/sda -h <server hostname>
+
+to connect and transfer data over the network.
-Which will send the traces from tracehost to parsehost over the network on
-the defined port number.
Documentation
-------------