From e2d127db234d98d60c04637a87404393602676a3 Mon Sep 17 00:00:00 2001 From: mpiehl Date: Sun, 28 Sep 2014 20:29:40 -0500 Subject: [PATCH] Fixed a couple minor documentation issues --- examples/iosnoop_example.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/iosnoop_example.txt b/examples/iosnoop_example.txt index 0f7b076..a47a32c 100644 --- a/examples/iosnoop_example.txt +++ b/examples/iosnoop_example.txt @@ -132,7 +132,7 @@ subsystem). You can try the -Q option for more reliable process identification. The -Q option begins tracing on block I/O queue insert, instead of issue. Here's before and after, while dd(1) writes a large file: -# .liosnoop +# ./iosnoop Tracing block I/O. Ctrl-C to end. COMM PID TYPE DEV BLOCK BYTES LATms dd 26983 WS 202,16 4064416 45056 16.70 @@ -162,7 +162,7 @@ when the block device I/O was issued, but they didn't originate it. Now the -Q option is used: -# .liosnoop -Q +# ./iosnoop -Q Tracing block I/O. Ctrl-C to end. COMM PID TYPE DEV BLOCK BYTES LATms kjournald 1217 WS 202,16 6132200 45056 141.12