updated sleepingBeauties.meta, regenerated index

8 files changed, 49 insertions, 47 deletions

diff --git a/testsuite/systemtap.examples/ChangeLog b/testsuite/systemtap.examples/ChangeLog
index ac8b0d0e..25d02a2a 100644
--- a/testsuite/systemtap.examples/ChangeLog
+++ b/testsuite/systemtap.examples/ChangeLog
@@ -1,3 +1,7 @@
+2008-11-19  Frank Ch. Eigler  <fche@elastic.org>
+
+	* process/sleepingBeauties.meta: Updated description.
+
 2008-10-27  William Cohen  <wcohen@redhat.com>
 
 	* io/traceio2.stp: Use local variable available from vfs tapset.
diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html
index d6b1c99b..54305057 100644
--- a/testsuite/systemtap.examples/index.html
+++ b/testsuite/systemtap.examples/index.html
@@ -93,8 +93,8 @@ subsystems: signals, keywords: signals<br>
 subsystems: signals, keywords: signals<br>
 <p>The script watches for a particular signal sent to a specific process. When that signal is sent to the specified process, the script prints out the PID and executable of the process sending the signal, the PID and executable name of the process receiving the signal, and the signal number and name.</p></li>
 <li><a href="process/sleepingBeauties.stp">process/sleepingBeauties.stp</a> - Generating Backtraces of Threads Waiting for IO Operations<br>
-subsystems: scheduler, keywords: io scheduler<br>
-<p>The script monitor time threads spend waiting for IO operations (in "D" state) in the wait_for_completion function. If a thread spends over 10ms wall-clock time waiting, information is printed out describing the thread number and executable name. When slow the wait_for_completion function complete, backtraces for the long duration calls are printed out.</p></li>
+subsystems: scheduler, keywords: io scheduler backtrace<br>
+<p>The script monitors the time that threads spend waiting for IO operations (in "D" state) in the wait_for_completion function.  If a thread spends over 10ms, its name and backtrace is printed, and later so is the total delay.</p></li>
 <li><a href="process/sleeptime.stp">process/sleeptime.stp</a> - Trace Time Spent in nanosleep Syscalls<br>
 subsystems: syscall, keywords: syscall sleep<br>
 <p>The script watches each nanosleep syscall on the system. At the end of each nanosleep syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in paretheses, the "nanosleep:" key, and the duration of the sleep in microseconds.</p></li>
diff --git a/testsuite/systemtap.examples/index.txt b/testsuite/systemtap.examples/index.txt
index 1372afb0..72ae3633 100644
--- a/testsuite/systemtap.examples/index.txt
+++ b/testsuite/systemtap.examples/index.txt
@@ -148,14 +148,12 @@ subsystems: signals, keywords: signals
 
 
 process/sleepingBeauties.stp - Generating Backtraces of Threads Waiting for IO Operations
-subsystems: scheduler, keywords: io scheduler
-
-  The script monitor time threads spend waiting for IO operations (in
-  "D" state) in the wait_for_completion function. If a thread spends
-  over 10ms wall-clock time waiting, information is printed out
-  describing the thread number and executable name. When slow the
-  wait_for_completion function complete, backtraces for the long
-  duration calls are printed out.
+subsystems: scheduler, keywords: io scheduler backtrace
+
+  The script monitors the time that threads spend waiting for IO
+  operations (in "D" state) in the wait_for_completion function.  If a
+  thread spends over 10ms, its name and backtrace is printed, and later
+  so is the total delay.
 
 
 process/sleeptime.stp - Trace Time Spent in nanosleep Syscalls
diff --git a/testsuite/systemtap.examples/keyword-index.html b/testsuite/systemtap.examples/keyword-index.html
index 2825bc2e..8a673c2f 100644
--- a/testsuite/systemtap.examples/keyword-index.html
+++ b/testsuite/systemtap.examples/keyword-index.html
@@ -46,6 +46,9 @@
 <li><a href="io/io_submit.stp">io/io_submit.stp</a> - Tally Reschedule Reason During AIO io_submit Call<br>
 subsystems: io, keywords: io backtrace<br>
 <p>When a reschedule occurs during an AIO io_submit call, accumulate the traceback in a histogram. When the script exits prints out a sorted list from most common to least common backtrace.</p></li>
+<li><a href="process/sleepingBeauties.stp">process/sleepingBeauties.stp</a> - Generating Backtraces of Threads Waiting for IO Operations<br>
+subsystems: scheduler, keywords: io scheduler backtrace<br>
+<p>The script monitors the time that threads spend waiting for IO operations (in "D" state) in the wait_for_completion function.  If a thread spends over 10ms, its name and backtrace is printed, and later so is the total delay.</p></li>
 </ul>
 <h3><a name="CALLGRAPH">CALLGRAPH</a></h3>
 <ul>
@@ -104,8 +107,8 @@ subsystems: io, keywords: io<br>
 subsystems: io, keywords: io<br>
 <p>Print out the executable name and process number as reads and writes to the specified device occur.</p></li>
 <li><a href="process/sleepingBeauties.stp">process/sleepingBeauties.stp</a> - Generating Backtraces of Threads Waiting for IO Operations<br>
-subsystems: scheduler, keywords: io scheduler<br>
-<p>The script monitor time threads spend waiting for IO operations (in "D" state) in the wait_for_completion function. If a thread spends over 10ms wall-clock time waiting, information is printed out describing the thread number and executable name. When slow the wait_for_completion function complete, backtraces for the long duration calls are printed out.</p></li>
+subsystems: scheduler, keywords: io scheduler backtrace<br>
+<p>The script monitors the time that threads spend waiting for IO operations (in "D" state) in the wait_for_completion function.  If a thread spends over 10ms, its name and backtrace is printed, and later so is the total delay.</p></li>
 </ul>
 <h3><a name="LOCKING">LOCKING</a></h3>
 <ul>
@@ -149,8 +152,8 @@ subsystems: syscall, keywords: syscall read write time io<br>
 <h3><a name="SCHEDULER">SCHEDULER</a></h3>
 <ul>
 <li><a href="process/sleepingBeauties.stp">process/sleepingBeauties.stp</a> - Generating Backtraces of Threads Waiting for IO Operations<br>
-subsystems: scheduler, keywords: io scheduler<br>
-<p>The script monitor time threads spend waiting for IO operations (in "D" state) in the wait_for_completion function. If a thread spends over 10ms wall-clock time waiting, information is printed out describing the thread number and executable name. When slow the wait_for_completion function complete, backtraces for the long duration calls are printed out.</p></li>
+subsystems: scheduler, keywords: io scheduler backtrace<br>
+<p>The script monitors the time that threads spend waiting for IO operations (in "D" state) in the wait_for_completion function.  If a thread spends over 10ms, its name and backtrace is printed, and later so is the total delay.</p></li>
 </ul>
 <h3><a name="SIGNALS">SIGNALS</a></h3>
 <ul>
diff --git a/testsuite/systemtap.examples/keyword-index.txt b/testsuite/systemtap.examples/keyword-index.txt
index 22065e76..470e7c45 100644
--- a/testsuite/systemtap.examples/keyword-index.txt
+++ b/testsuite/systemtap.examples/keyword-index.txt
@@ -11,6 +11,15 @@ subsystems: io, keywords: io backtrace
   list from most common to least common backtrace.
 
 
+process/sleepingBeauties.stp - Generating Backtraces of Threads Waiting for IO Operations
+subsystems: scheduler, keywords: io scheduler backtrace
+
+  The script monitors the time that threads spend waiting for IO
+  operations (in "D" state) in the wait_for_completion function.  If a
+  thread spends over 10ms, its name and backtrace is printed, and later
+  so is the total delay.
+
+
 = CALLGRAPH =
 
 general/para-callgraph.stp - Callgraph tracing with arguments
@@ -132,14 +141,12 @@ subsystems: io, keywords: io
 
 
 process/sleepingBeauties.stp - Generating Backtraces of Threads Waiting for IO Operations
-subsystems: scheduler, keywords: io scheduler
+subsystems: scheduler, keywords: io scheduler backtrace
 
-  The script monitor time threads spend waiting for IO operations (in
-  "D" state) in the wait_for_completion function. If a thread spends
-  over 10ms wall-clock time waiting, information is printed out
-  describing the thread number and executable name. When slow the
-  wait_for_completion function complete, backtraces for the long
-  duration calls are printed out.
+  The script monitors the time that threads spend waiting for IO
+  operations (in "D" state) in the wait_for_completion function.  If a
+  thread spends over 10ms, its name and backtrace is printed, and later
+  so is the total delay.
 
 
 = LOCKING =
@@ -236,14 +243,12 @@ subsystems: syscall, keywords: syscall read write time io
 = SCHEDULER =
 
 process/sleepingBeauties.stp - Generating Backtraces of Threads Waiting for IO Operations
-subsystems: scheduler, keywords: io scheduler
-
-  The script monitor time threads spend waiting for IO operations (in
-  "D" state) in the wait_for_completion function. If a thread spends
-  over 10ms wall-clock time waiting, information is printed out
-  describing the thread number and executable name. When slow the
-  wait_for_completion function complete, backtraces for the long
-  duration calls are printed out.
+subsystems: scheduler, keywords: io scheduler backtrace
+
+  The script monitors the time that threads spend waiting for IO
+  operations (in "D" state) in the wait_for_completion function.  If a
+  thread spends over 10ms, its name and backtrace is printed, and later
+  so is the total delay.
 
 
 = SIGNALS =
diff --git a/testsuite/systemtap.examples/process/sleepingBeauties.meta b/testsuite/systemtap.examples/process/sleepingBeauties.meta
index 95e08361..3338edbf 100644
--- a/testsuite/systemtap.examples/process/sleepingBeauties.meta
+++ b/testsuite/systemtap.examples/process/sleepingBeauties.meta
@@ -1,13 +1,7 @@
 title: Generating Backtraces of Threads Waiting for IO Operations
 name: sleepingBeauties.stp
-version: 1.0
-author: anonymous
-keywords: io scheduler
+keywords: io scheduler backtrace
 subsystem: scheduler
-status: production
-exit: user-controlled
-output: trace
-scope: system-wide
-description: The script monitor time threads spend waiting for IO operations (in "D" state) in the wait_for_completion function. If a thread spends over 10ms wall-clock time waiting, information is printed out describing the thread number and executable name. When slow the wait_for_completion function complete, backtraces for the long duration calls are printed out.
+description: The script monitors the time that threads spend waiting for IO operations (in "D" state) in the wait_for_completion function.  If a thread spends over 10ms, its name and backtrace is printed, and later so is the total delay.
 test_check: stap -p4 sleepingBeauties.stp
 test_installcheck: stap sleepingBeauties.stp -c "sleep 1"
diff --git a/testsuite/systemtap.examples/subsystem-index.html b/testsuite/systemtap.examples/subsystem-index.html
index 0f2517ce..ef07ccec 100644
--- a/testsuite/systemtap.examples/subsystem-index.html
+++ b/testsuite/systemtap.examples/subsystem-index.html
@@ -113,8 +113,8 @@ subsystems: none, keywords: simple<br>
 <h3><a name="SCHEDULER">SCHEDULER</a></h3>
 <ul>
 <li><a href="process/sleepingBeauties.stp">process/sleepingBeauties.stp</a> - Generating Backtraces of Threads Waiting for IO Operations<br>
-subsystems: scheduler, keywords: io scheduler<br>
-<p>The script monitor time threads spend waiting for IO operations (in "D" state) in the wait_for_completion function. If a thread spends over 10ms wall-clock time waiting, information is printed out describing the thread number and executable name. When slow the wait_for_completion function complete, backtraces for the long duration calls are printed out.</p></li>
+subsystems: scheduler, keywords: io scheduler backtrace<br>
+<p>The script monitors the time that threads spend waiting for IO operations (in "D" state) in the wait_for_completion function.  If a thread spends over 10ms, its name and backtrace is printed, and later so is the total delay.</p></li>
 </ul>
 <h3><a name="SIGNALS">SIGNALS</a></h3>
 <ul>
diff --git a/testsuite/systemtap.examples/subsystem-index.txt b/testsuite/systemtap.examples/subsystem-index.txt
index d34ac64c..0e116a60 100644
--- a/testsuite/systemtap.examples/subsystem-index.txt
+++ b/testsuite/systemtap.examples/subsystem-index.txt
@@ -146,14 +146,12 @@ subsystems: none, keywords: simple
 = SCHEDULER =
 
 process/sleepingBeauties.stp - Generating Backtraces of Threads Waiting for IO Operations
-subsystems: scheduler, keywords: io scheduler
-
-  The script monitor time threads spend waiting for IO operations (in
-  "D" state) in the wait_for_completion function. If a thread spends
-  over 10ms wall-clock time waiting, information is printed out
-  describing the thread number and executable name. When slow the
-  wait_for_completion function complete, backtraces for the long
-  duration calls are printed out.
+subsystems: scheduler, keywords: io scheduler backtrace
+
+  The script monitors the time that threads spend waiting for IO
+  operations (in "D" state) in the wait_for_completion function.  If a
+  thread spends over 10ms, its name and backtrace is printed, and later
+  so is the total delay.
 
 
 = SIGNALS =