From 3bdb66294bfbe8c388cb6dea5e8f2a55971cb92b Mon Sep 17 00:00:00 2001 From: Breno Leitao Date: Wed, 16 Sep 2009 14:37:17 -0400 Subject: A network device example Add a example that cover the network device tapset. This example just add simple probes and display what is going one with all the network devices. Signed-off-by: Josh Stone --- testsuite/systemtap.examples/network/netdev.stp | 58 +++++++++++++++++++++++++ 1 file changed, 58 insertions(+) create mode 100755 testsuite/systemtap.examples/network/netdev.stp (limited to 'testsuite/systemtap.examples') diff --git a/testsuite/systemtap.examples/network/netdev.stp b/testsuite/systemtap.examples/network/netdev.stp new file mode 100755 index 00000000..64c8167a --- /dev/null +++ b/testsuite/systemtap.examples/network/netdev.stp @@ -0,0 +1,58 @@ +#! /usr/bin/env stap + +############################################################ +# netdev.stp +# Author: Breno Leitao +# An example script to show how a netdev works and its +# functions +############################################################ + + +probe netdev.get_stats{ + printf("%s was asked for statistics structure\n", dev_name) +} + +probe netdev.register{ + printf("Registering netdev_name %s\n", dev_name) +} + +probe netdev.unregister{ + printf("Unregistering netdev %s\n", dev_name) +} + +probe netdev.ioctl{ + printf("Netdev ioctl raised with param: %d and arg: %s\n", cmd, arg) +} + +probe netdev.set_promiscuity { + if (enable) + printf("Device %s entering in prosmicuous mode\n", dev_name) + else + printf("Device %s leaving prosmicuous mode\n", dev_name) +} + +probe netdev.change_rx_flag { + printf("Device %s is changing its RX flags to %d\n", dev_name, flags) +} + +probe netdev.change_mtu { + printf("Changing MTU on device %s from %d to %d\n", dev_name, + old_mtu, new_mtu) +} + +probe netdev.change_mac { + printf("Changing MAC adddres on device %s from %s to %s\n", + dev_name, old_mac, new_mac) +} + +probe netdev.transmit { + printf("Device %s is sending (queued) a packet with protocol %d\n", dev_name, protocol) +} + +probe netdev.hard_transmit { + printf("Device %s is sending (hard) a packet with protocol %d\n", dev_name, protocol) +} + +probe netdev.rx { + printf("Device %s received a packet with protocol %d\n", dev_name, protocol) +} -- cgit From 53e5699fe863f0a122c73782b4465296e3adc131 Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Wed, 16 Sep 2009 14:17:10 -0700 Subject: Add meta for the netdev example & regenerate indexes --- testsuite/systemtap.examples/index.html | 3 +++ testsuite/systemtap.examples/index.txt | 7 +++++++ testsuite/systemtap.examples/keyword-index.html | 14 +++++++++++++- testsuite/systemtap.examples/keyword-index.txt | 23 +++++++++++++++++++++++ testsuite/systemtap.examples/network/netdev.meta | 13 +++++++++++++ 5 files changed, 59 insertions(+), 1 deletion(-) create mode 100644 testsuite/systemtap.examples/network/netdev.meta (limited to 'testsuite/systemtap.examples') diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html index b079f5b8..d3efe7fa 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -121,6 +121,9 @@ keywords: NETWORK network/dropwatch.stp - Watch Where Socket Buffers are Freed in the Kernel
keywords: NETWORK TRACEPOINT BUFFER FREE

Every five seconds the dropwatch.stp script lists the number of socket buffers freed at locations in the kernel.

+
  • network/netdev.stp - Trace Activity on Network Devices
    +keywords: NETWORK DEVICE TRAFFIC
    +

    The netdev.stp script traces configuration and transmit/receive activity on network devices.

  • network/nettop.stp - Periodic Listing of Processes Using Network Interfaces
    keywords: NETWORK TRAFFIC PER-PROCESS

    Every five seconds the nettop.stp script prints out a list of processed (PID and command) with the number of packets sent/received and the amount of data sent/received by the process during that interval.

    • diff --git a/testsuite/systemtap.examples/index.txt b/testsuite/systemtap.examples/index.txt index 376c545e..ad0c1935 100644 --- a/testsuite/systemtap.examples/index.txt +++ b/testsuite/systemtap.examples/index.txt @@ -264,6 +264,13 @@ keywords: network tracepoint buffer free socket buffers freed at locations in the kernel. +network/netdev.stp - Trace Activity on Network Devices +keywords: network device traffic + + The netdev.stp script traces configuration and transmit/receive + activity on network devices. + + network/nettop.stp - Periodic Listing of Processes Using Network Interfaces keywords: network traffic per-process diff --git a/testsuite/systemtap.examples/keyword-index.html b/testsuite/systemtap.examples/keyword-index.html index a57b967e..a57a73b1 100644 --- a/testsuite/systemtap.examples/keyword-index.html +++ b/testsuite/systemtap.examples/keyword-index.html @@ -39,7 +39,7 @@

    Examples by Keyword

    -

    AUTOFS BACKTRACE BUFFER CALLGRAPH CPU DISK FORMAT FREE FUNCTIONS FUTEX GRAPH INTERRUPT IO LOCKING MEMORY MONITOR NETWORK NFS NUMA PER-PROCESS PROCESS PROFILING READ SCHEDULER SCSI SIGNALS SIMPLE SLEEP SOCKET STATISTICS SYSCALL TCP TIME TRACE TRACEPOINT TRAFFIC TTY USE WAIT4 WRITE

    +

    AUTOFS BACKTRACE BUFFER CALLGRAPH CPU DEVICE DISK FORMAT FREE FUNCTIONS FUTEX GRAPH INTERRUPT IO LOCKING MEMORY MONITOR NETWORK NFS NUMA PER-PROCESS PROCESS PROFILING READ SCHEDULER SCSI SIGNALS SIMPLE SLEEP SOCKET STATISTICS SYSCALL TCP TIME TRACE TRACEPOINT TRAFFIC TTY USE WAIT4 WRITE

    AUTOFS

    • network/autofs4.stp - Watch autofs4 operations
      @@ -79,6 +79,12 @@ keywords: TRACE DISK CPU USE GRAPH

      The script tracks the disk and CPU utilization. The resulting output of the script can be piped into gnuplot to generate a graph of disk and CPU USE.

    +

    DEVICE

    +

    DISK

    • general/graphs.stp - Graphing Disk and CPU Utilization
      @@ -213,6 +219,9 @@ keywords: NETWORK network/dropwatch.stp - Watch Where Socket Buffers are Freed in the Kernel
      keywords: NETWORK TRACEPOINT BUFFER FREE

      Every five seconds the dropwatch.stp script lists the number of socket buffers freed at locations in the kernel.

      • +
    • network/netdev.stp - Trace Activity on Network Devices
      +keywords: NETWORK DEVICE TRAFFIC
      +

      The netdev.stp script traces configuration and transmit/receive activity on network devices.

    • network/nettop.stp - Periodic Listing of Processes Using Network Interfaces
      keywords: NETWORK TRAFFIC PER-PROCESS

      Every five seconds the nettop.stp script prints out a list of processed (PID and command) with the number of packets sent/received and the amount of data sent/received by the process during that interval.

      • @@ -420,6 +429,9 @@ keywords: PROCESS TRAFFIC
        +
      • network/netdev.stp - Trace Activity on Network Devices
        +keywords: NETWORK DEVICE TRAFFIC
        +

        The netdev.stp script traces configuration and transmit/receive activity on network devices.

      • network/nettop.stp - Periodic Listing of Processes Using Network Interfaces
        keywords: NETWORK TRAFFIC PER-PROCESS

        Every five seconds the nettop.stp script prints out a list of processed (PID and command) with the number of packets sent/received and the amount of data sent/received by the process during that interval.

        • diff --git a/testsuite/systemtap.examples/keyword-index.txt b/testsuite/systemtap.examples/keyword-index.txt index 4f1ce8f2..331e9da5 100644 --- a/testsuite/systemtap.examples/keyword-index.txt +++ b/testsuite/systemtap.examples/keyword-index.txt @@ -80,6 +80,15 @@ keywords: disk cpu use graph and CPU USE. += DEVICE = + +network/netdev.stp - Trace Activity on Network Devices +keywords: network device traffic + + The netdev.stp script traces configuration and transmit/receive + activity on network devices. + + = DISK = general/graphs.stp - Graphing Disk and CPU Utilization @@ -418,6 +427,13 @@ keywords: network tracepoint buffer free socket buffers freed at locations in the kernel. +network/netdev.stp - Trace Activity on Network Devices +keywords: network device traffic + + The netdev.stp script traces configuration and transmit/receive + activity on network devices. + + network/nettop.stp - Periodic Listing of Processes Using Network Interfaces keywords: network traffic per-process @@ -937,6 +953,13 @@ keywords: process scheduler time tracepoint = TRAFFIC = +network/netdev.stp - Trace Activity on Network Devices +keywords: network device traffic + + The netdev.stp script traces configuration and transmit/receive + activity on network devices. + + network/nettop.stp - Periodic Listing of Processes Using Network Interfaces keywords: network traffic per-process diff --git a/testsuite/systemtap.examples/network/netdev.meta b/testsuite/systemtap.examples/network/netdev.meta new file mode 100644 index 00000000..e467a66a --- /dev/null +++ b/testsuite/systemtap.examples/network/netdev.meta @@ -0,0 +1,13 @@ +title: Trace Activity on Network Devices +name: netdev.stp +version: 1.0 +author: Breno Leitao +keywords: network device traffic +subsystem: network +status: production +exit: user-controlled +output: trace +scope: system-wide +description: The netdev.stp script traces configuration and transmit/receive activity on network devices. +test_check: stap -p4 netdev.stp +test_installcheck: stap netdev.stp -c "sleep 0.2" -- cgit From ad7e33d7ceb3251f5141b586dad4f824c519d757 Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Wed, 16 Sep 2009 15:16:47 -0700 Subject: Spelling fixes in the meta of many examples --- testsuite/systemtap.examples/index.html | 22 +++++------ testsuite/systemtap.examples/index.txt | 26 ++++++------- testsuite/systemtap.examples/io/ioblktime.meta | 2 +- testsuite/systemtap.examples/io/iostat-scsi.meta | 2 +- testsuite/systemtap.examples/io/iotime.meta | 2 +- testsuite/systemtap.examples/keyword-index.html | 40 ++++++++++---------- testsuite/systemtap.examples/keyword-index.txt | 44 +++++++++++----------- testsuite/systemtap.examples/memory/mmreclaim.meta | 2 +- .../systemtap.examples/memory/mmwriteback.meta | 2 +- .../systemtap.examples/memory/numa_faults.meta | 2 +- testsuite/systemtap.examples/memory/pfaults.meta | 2 +- testsuite/systemtap.examples/network/netdev.stp | 6 +-- testsuite/systemtap.examples/process/sigkill.meta | 2 +- .../systemtap.examples/process/sleeptime.meta | 2 +- .../process/syscalls_by_proc.meta | 2 +- .../systemtap.examples/process/wait4time.meta | 2 +- 16 files changed, 80 insertions(+), 80 deletions(-) (limited to 'testsuite/systemtap.examples') diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html index d3efe7fa..203bc5d4 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -66,16 +66,16 @@ keywords: IO io/ioblktime.stp - Average Time Block IO Requests Spend in Queue
        keywords: IO
        -

        The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average time waiting time for block IO per device and prints list every 10 seconds. In some cases there can be too many oustanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command line.

        +

        The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average time waiting time for block IO per device and prints list every 10 seconds. In some cases there can be too many outstanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command line.

      • io/iostat-scsi.stp - iostat for SCSI Devices
        keywords: IO PROFILING SCSI
        -

        The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the various machines's SCSI devices. The script takes one argument which is the number of seconds between reports.

        • +

        The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports.

      • io/iostats.stp - List Executables Reading and Writing the Most Data
        keywords: IO PROFILING

        The iostat.stp script measures the amount of data successfully read and written by all the executables on the system. The output is sorted from most greatest sum of bytes read and written by an executable to the least. The output contains the count of operations (opens, reads, and writes), the totals and averages for the number of bytes read and written.

      • io/iotime.stp - Trace Time Spent in Read and Write for Files
        keywords: SYSCALL READ WRITE TIME IO
        -

        The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parenthesese. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

        • +

        The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

      • io/iotop.stp - Periodically Print I/O Activity by Process Name
        keywords: IO

        Every five seconds print out the top ten executables generating I/O traffic during that interval sorted in descending order.

        • @@ -105,16 +105,16 @@ keywords: MEMORY

        The mmfilepage.stp script uses the virtual memory tracepoints available in some kernels to track the number of faults, copy on writes mapping, and unmapping operations for file backed pages. When the script is terminated the counts are printed for each process that allocated pages while the script was running. The mmfilepage.stp script is useful in debugging leaks in the mapped file regions of a process.

      • memory/mmreclaim.stp - Track Virtual Memory System Page Reclamation
        keywords: MEMORY
        -

        The mmreclaim.stp script uses the virtual memory tracepoints available in some kernels to track page reclaim activity that occured while the script was running. Its useful is debugging performance problems that occur due to page reclamation.

        • +

        The mmreclaim.stp script uses the virtual memory tracepoints available in some kernels to track page reclaim activity that occurred while the script was running. Its useful is debugging performance problems that occur due to page reclamation.

      • memory/mmwriteback.stp - Track Virtual Memory System Writing to Disk
        keywords: MEMORY
        -

        The mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a supposedly idle system that is experiencing upexpected IO.

        • +

        The mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a supposedly idle system that is experiencing unexpected IO.

      • memory/numa_faults.stp - Summarize Process Misses across NUMA Nodes
        keywords: MEMORY NUMA
        -

        The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also providea a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer.

        • +

        The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer.

      • memory/pfaults.stp - Generate Log of Major and Minor Page Faults
        keywords: MEMORY
        -

        The pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to determine where the page faults are occuring.

        • +

        The pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to determine where the page faults are occurring.

      • network/autofs4.stp - Watch autofs4 operations
        keywords: NETWORK AUTOFS NFS

        Trace key autofs4 operations such as mounting or unmounting remote filesystems.

        • @@ -171,7 +171,7 @@ keywords: SIGNALS

        Print signal counts by process name in descending order.

      • process/sigkill.stp - Track SIGKILL Signals
        keywords: SIGNALS
        -

        The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the desination executable and process ID, the executable name user ID that sent the signal.

        • +

        The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the destination executable and process ID, the executable name user ID that sent the signal.

      • process/sigmon.stp - Track a particular signal to a specific process
        keywords: SIGNALS

        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.

        • @@ -180,16 +180,16 @@ keywords: IO
      • process/sleeptime.stp - Trace Time Spent in nanosleep Syscalls
        keywords: SYSCALL SLEEP
        -

        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.

        • +

        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 parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds.

      • process/syscalls_by_pid.stp - System-Wide Count of Syscalls by PID
        keywords: SYSCALL

        The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each PID ordered from greatest to least number of syscalls.

      • process/syscalls_by_proc.stp - System-Wide Count of Syscalls by Executable
        keywords: SYSCALL
        -

        The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each executable ordered from greates to least number of syscalls.

        • +

        The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each executable ordered from greatest to least number of syscalls.

      • process/wait4time.stp - Trace Time Spent in wait4 Syscalls
        keywords: SYSCALL WAIT4
        -

        The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in paretheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1".

        • +

        The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in parentheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1".

      • profiling/functioncallcount.stp - Count Times Functions Called
        keywords: PROFILING FUNCTIONS

        The functioncallcount.stp script takes one argument, a list of functions to probe. The script will run and count the number of times that each of the functions on the list is called. On exit the script will print a sorted list from most frequently to least frequently called function.

        • diff --git a/testsuite/systemtap.examples/index.txt b/testsuite/systemtap.examples/index.txt index ad0c1935..20b4da4f 100644 --- a/testsuite/systemtap.examples/index.txt +++ b/testsuite/systemtap.examples/index.txt @@ -74,7 +74,7 @@ keywords: io The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average time waiting time for block IO per device and prints list - every 10 seconds. In some cases there can be too many oustanding + every 10 seconds. In some cases there can be too many outstanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command @@ -85,7 +85,7 @@ io/iostat-scsi.stp - iostat for SCSI Devices keywords: io profiling scsi The iostat-scsi.stp script provides a breakdown of the number of blks - read and written on the various machines's SCSI devices. The script + read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports. @@ -109,7 +109,7 @@ keywords: syscall read write time io number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in - parenthesese. The first line with the "access" keyword lists the file + parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write @@ -212,9 +212,9 @@ memory/mmreclaim.stp - Track Virtual Memory System Page Reclamation keywords: memory The mmreclaim.stp script uses the virtual memory tracepoints - available in some kernels to track page reclaim activity that occured - while the script was running. Its useful is debugging performance - problems that occur due to page reclamation. + available in some kernels to track page reclaim activity that + occurred while the script was running. Its useful is debugging + performance problems that occur due to page reclamation. memory/mmwriteback.stp - Track Virtual Memory System Writing to Disk @@ -224,7 +224,7 @@ keywords: memory available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a - supposedly idle system that is experiencing upexpected IO. + supposedly idle system that is experiencing unexpected IO. memory/numa_faults.stp - Summarize Process Misses across NUMA Nodes @@ -232,7 +232,7 @@ keywords: memory numa The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and - write pages faults for each process. The script also providea a break + write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer. @@ -247,7 +247,7 @@ keywords: memory completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to - determine where the page faults are occuring. + determine where the page faults are occurring. network/autofs4.stp - Watch autofs4 operations @@ -412,7 +412,7 @@ keywords: signals The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the - desination executable and process ID, the executable name user ID + destination executable and process ID, the executable name user ID that sent the signal. @@ -441,7 +441,7 @@ keywords: syscall sleep 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 + parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds. @@ -458,7 +458,7 @@ keywords: syscall The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each - executable ordered from greates to least number of syscalls. + executable ordered from greatest to least number of syscalls. process/wait4time.stp - Trace Time Spent in wait4 Syscalls @@ -466,7 +466,7 @@ keywords: syscall wait4 The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in - microseconds, the pid, the executable name in paretheses, the + microseconds, the pid, the executable name in parentheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1". diff --git a/testsuite/systemtap.examples/io/ioblktime.meta b/testsuite/systemtap.examples/io/ioblktime.meta index 09425b29..01f34295 100644 --- a/testsuite/systemtap.examples/io/ioblktime.meta +++ b/testsuite/systemtap.examples/io/ioblktime.meta @@ -8,6 +8,6 @@ status: production exit: user-controlled output: sorted-list scope: system-wide -description: The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average time waiting time for block IO per device and prints list every 10 seconds. In some cases there can be too many oustanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command line. +description: The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average time waiting time for block IO per device and prints list every 10 seconds. In some cases there can be too many outstanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command line. test_check: stap -p4 ioblktime.stp test_installcheck: stap ioblktime.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/io/iostat-scsi.meta b/testsuite/systemtap.examples/io/iostat-scsi.meta index a992bd51..a5fe7a8f 100644 --- a/testsuite/systemtap.examples/io/iostat-scsi.meta +++ b/testsuite/systemtap.examples/io/iostat-scsi.meta @@ -8,7 +8,7 @@ status: production exit: user-controlled output: timed scope: system-wide -description: The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the various machines's SCSI devices. The script takes one argument which is the number of seconds between reports. +description: The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports. test_support: stap -l module("st").function("st_do_scsi")!,kernel.function("st_do_scsi") test_check: stap -g -p4 iostat-scsi.stp 1 test_installcheck: stap -g iostat-scsi.stp 1 -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/io/iotime.meta b/testsuite/systemtap.examples/io/iotime.meta index cde49974..cf22eacf 100644 --- a/testsuite/systemtap.examples/io/iotime.meta +++ b/testsuite/systemtap.examples/io/iotime.meta @@ -8,6 +8,6 @@ status: production exit: user-controlled output: trace scope: system-wide -description: The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parenthesese. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls. +description: The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls. test_check: stap -p4 iotime.stp test_installcheck: stap iotime.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/keyword-index.html b/testsuite/systemtap.examples/keyword-index.html index a57a73b1..b59ce4a8 100644 --- a/testsuite/systemtap.examples/keyword-index.html +++ b/testsuite/systemtap.examples/keyword-index.html @@ -140,16 +140,16 @@ keywords: IO io/ioblktime.stp - Average Time Block IO Requests Spend in Queue
        keywords: IO
        -

        The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average time waiting time for block IO per device and prints list every 10 seconds. In some cases there can be too many oustanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command line.

        +

        The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average time waiting time for block IO per device and prints list every 10 seconds. In some cases there can be too many outstanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command line.

      • io/iostat-scsi.stp - iostat for SCSI Devices
        keywords: IO PROFILING SCSI
        -

        The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the various machines's SCSI devices. The script takes one argument which is the number of seconds between reports.

        • +

        The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports.

      • io/iostats.stp - List Executables Reading and Writing the Most Data
        keywords: IO PROFILING

        The iostat.stp script measures the amount of data successfully read and written by all the executables on the system. The output is sorted from most greatest sum of bytes read and written by an executable to the least. The output contains the count of operations (opens, reads, and writes), the totals and averages for the number of bytes read and written.

      • io/iotime.stp - Trace Time Spent in Read and Write for Files
        keywords: SYSCALL READ WRITE TIME IO
        -

        The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parenthesese. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

        • +

        The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

      • io/iotop.stp - Periodically Print I/O Activity by Process Name
        keywords: IO

        Every five seconds print out the top ten executables generating I/O traffic during that interval sorted in descending order.

        • @@ -191,16 +191,16 @@ keywords: MEMORY

        The mmfilepage.stp script uses the virtual memory tracepoints available in some kernels to track the number of faults, copy on writes mapping, and unmapping operations for file backed pages. When the script is terminated the counts are printed for each process that allocated pages while the script was running. The mmfilepage.stp script is useful in debugging leaks in the mapped file regions of a process.

      • memory/mmreclaim.stp - Track Virtual Memory System Page Reclamation
        keywords: MEMORY
        -

        The mmreclaim.stp script uses the virtual memory tracepoints available in some kernels to track page reclaim activity that occured while the script was running. Its useful is debugging performance problems that occur due to page reclamation.

        • +

        The mmreclaim.stp script uses the virtual memory tracepoints available in some kernels to track page reclaim activity that occurred while the script was running. Its useful is debugging performance problems that occur due to page reclamation.

      • memory/mmwriteback.stp - Track Virtual Memory System Writing to Disk
        keywords: MEMORY
        -

        The mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a supposedly idle system that is experiencing upexpected IO.

        • +

        The mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a supposedly idle system that is experiencing unexpected IO.

      • memory/numa_faults.stp - Summarize Process Misses across NUMA Nodes
        keywords: MEMORY NUMA
        -

        The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also providea a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer.

        • +

        The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer.

      • memory/pfaults.stp - Generate Log of Major and Minor Page Faults
        keywords: MEMORY
        -

        The pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to determine where the page faults are occuring.

        • +

        The pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to determine where the page faults are occurring.

      • network/sk_stream_wait_memory.stp - Track Start and Stop of Processes Due to Network Buffer Space
        keywords: NETWORK TCP BUFFER MEMORY

        The sk_stream-wait_memory.stp prints a time stamp, executable, and pid each time a process blocks due to the send buffer being full. A similar entry is printed each time a process continues because there is room in the buffer.

        • @@ -251,7 +251,7 @@ keywords: NETWORK memory/numa_faults.stp - Summarize Process Misses across NUMA Nodes
        keywords: MEMORY NUMA
        -

        The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also providea a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer.

        +

        The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer.

      PER-PROCESS

        @@ -278,7 +278,7 @@ keywords: PROCESS io/iostat-scsi.stp - iostat for SCSI Devices
        keywords: IO PROFILING SCSI
        -

        The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the various machines's SCSI devices. The script takes one argument which is the number of seconds between reports.

        +

        The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports.

      • io/iostats.stp - List Executables Reading and Writing the Most Data
        keywords: IO PROFILING

        The iostat.stp script measures the amount of data successfully read and written by all the executables on the system. The output is sorted from most greatest sum of bytes read and written by an executable to the least. The output contains the count of operations (opens, reads, and writes), the totals and averages for the number of bytes read and written.

        • @@ -302,7 +302,7 @@ keywords: PROFILING
        • io/iotime.stp - Trace Time Spent in Read and Write for Files
          keywords: SYSCALL READ WRITE TIME IO
          -

          The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parenthesese. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

          • +

          The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

        SCHEDULER

          @@ -326,7 +326,7 @@ keywords: IO io/iostat-scsi.stp - iostat for SCSI Devices
          keywords: IO PROFILING SCSI
          -

          The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the various machines's SCSI devices. The script takes one argument which is the number of seconds between reports.

          +

          The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports.

        SIGNALS

          @@ -338,7 +338,7 @@ keywords: SIGNALS

          Print signal counts by process name in descending order.

        • process/sigkill.stp - Track SIGKILL Signals
          keywords: SIGNALS
          -

          The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the desination executable and process ID, the executable name user ID that sent the signal.

          • +

          The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the destination executable and process ID, the executable name user ID that sent the signal.

        • process/sigmon.stp - Track a particular signal to a specific process
          keywords: SIGNALS

          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.

          • @@ -353,7 +353,7 @@ keywords: SIMPLE
          • process/sleeptime.stp - Trace Time Spent in nanosleep Syscalls
            keywords: SYSCALL SLEEP
            -

            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.

            • +

            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 parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds.

          SOCKET

            @@ -374,7 +374,7 @@ keywords: NETWORK io/iotime.stp - Trace Time Spent in Read and Write for Files
            keywords: SYSCALL READ WRITE TIME IO
            -

            The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parenthesese. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

            +

            The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

          • process/errsnoop.stp - tabulate system call errors
            keywords: PROCESS SYSCALL

            The script prints a periodic tabular report about failing system calls, by process and by syscall failure. The first optional argument specifies the reporting interval (in seconds, default 5); the second optional argument gives a screen height (number of lines in the report, default 20).

            • @@ -383,16 +383,16 @@ keywords: SYSCALL process/sleeptime.stp - Trace Time Spent in nanosleep Syscalls
            keywords: SYSCALL SLEEP
            -

            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.

            +

            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 parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds.

          • process/syscalls_by_pid.stp - System-Wide Count of Syscalls by PID
            keywords: SYSCALL

            The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each PID ordered from greatest to least number of syscalls.

          • process/syscalls_by_proc.stp - System-Wide Count of Syscalls by Executable
            keywords: SYSCALL
            -

            The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each executable ordered from greates to least number of syscalls.

            • +

            The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each executable ordered from greatest to least number of syscalls.

          • process/wait4time.stp - Trace Time Spent in wait4 Syscalls
            keywords: SYSCALL WAIT4
            -

            The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in paretheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1".

            • +

            The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in parentheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1".

          TCP

            @@ -407,7 +407,7 @@ keywords: NETWORK io/iotime.stp - Trace Time Spent in Read and Write for Files
            keywords: SYSCALL READ WRITE TIME IO
            -

            The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parenthesese. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

            +

            The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

          • process/schedtimes.stp - Track Time Processes Spend in Various States using Tracepoints
            keywords: PROCESS SCHEDULER TIME TRACEPOINT

            The schedtimes.stp script instruments the scheduler to track the amount of time that each process spends running, sleeping, queued, and waiting for io. On exit the script prints out the accumulated time for each state of processes observed. Optionally, this script can be used with the '-c' or '-x' options to focus on a specific PID.

            • @@ -455,13 +455,13 @@ keywords: DISK process/wait4time.stp - Trace Time Spent in wait4 Syscalls
            keywords: SYSCALL WAIT4
            -

            The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in paretheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1".

            +

            The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in parentheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1".

          WRITE

          • io/iotime.stp - Trace Time Spent in Read and Write for Files
            keywords: SYSCALL READ WRITE TIME IO
            -

            The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parenthesese. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

            • +

            The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spend in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write syscalls.

          diff --git a/testsuite/systemtap.examples/keyword-index.txt b/testsuite/systemtap.examples/keyword-index.txt index 331e9da5..81713991 100644 --- a/testsuite/systemtap.examples/keyword-index.txt +++ b/testsuite/systemtap.examples/keyword-index.txt @@ -194,7 +194,7 @@ keywords: io The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average time waiting time for block IO per device and prints list - every 10 seconds. In some cases there can be too many oustanding + every 10 seconds. In some cases there can be too many outstanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command @@ -205,7 +205,7 @@ io/iostat-scsi.stp - iostat for SCSI Devices keywords: io profiling scsi The iostat-scsi.stp script provides a breakdown of the number of blks - read and written on the various machines's SCSI devices. The script + read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports. @@ -229,7 +229,7 @@ keywords: syscall read write time io number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in - parenthesese. The first line with the "access" keyword lists the file + parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write @@ -354,9 +354,9 @@ memory/mmreclaim.stp - Track Virtual Memory System Page Reclamation keywords: memory The mmreclaim.stp script uses the virtual memory tracepoints - available in some kernels to track page reclaim activity that occured - while the script was running. Its useful is debugging performance - problems that occur due to page reclamation. + available in some kernels to track page reclaim activity that + occurred while the script was running. Its useful is debugging + performance problems that occur due to page reclamation. memory/mmwriteback.stp - Track Virtual Memory System Writing to Disk @@ -366,7 +366,7 @@ keywords: memory available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a - supposedly idle system that is experiencing upexpected IO. + supposedly idle system that is experiencing unexpected IO. memory/numa_faults.stp - Summarize Process Misses across NUMA Nodes @@ -374,7 +374,7 @@ keywords: memory numa The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and - write pages faults for each process. The script also providea a break + write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer. @@ -389,7 +389,7 @@ keywords: memory completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to - determine where the page faults are occuring. + determine where the page faults are occurring. network/sk_stream_wait_memory.stp - Track Start and Stop of Processes Due to Network Buffer Space @@ -506,7 +506,7 @@ keywords: memory numa The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and - write pages faults for each process. The script also providea a break + write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer. @@ -567,7 +567,7 @@ io/iostat-scsi.stp - iostat for SCSI Devices keywords: io profiling scsi The iostat-scsi.stp script provides a breakdown of the number of blks - read and written on the various machines's SCSI devices. The script + read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports. @@ -640,7 +640,7 @@ keywords: syscall read write time io number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in - parenthesese. The first line with the "access" keyword lists the file + parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write @@ -705,7 +705,7 @@ io/iostat-scsi.stp - iostat for SCSI Devices keywords: io profiling scsi The iostat-scsi.stp script provides a breakdown of the number of blks - read and written on the various machines's SCSI devices. The script + read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports. @@ -728,7 +728,7 @@ keywords: signals The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the - desination executable and process ID, the executable name user ID + destination executable and process ID, the executable name user ID that sent the signal. @@ -759,7 +759,7 @@ keywords: syscall sleep 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 + parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds. @@ -808,7 +808,7 @@ keywords: syscall read write time io number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in - parenthesese. The first line with the "access" keyword lists the file + parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write @@ -840,7 +840,7 @@ keywords: syscall sleep 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 + parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds. @@ -857,7 +857,7 @@ keywords: syscall The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each - executable ordered from greates to least number of syscalls. + executable ordered from greatest to least number of syscalls. process/wait4time.stp - Trace Time Spent in wait4 Syscalls @@ -865,7 +865,7 @@ keywords: syscall wait4 The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in - microseconds, the pid, the executable name in paretheses, the + microseconds, the pid, the executable name in parentheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1". @@ -902,7 +902,7 @@ keywords: syscall read write time io number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in - parenthesese. The first line with the "access" keyword lists the file + parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write @@ -1004,7 +1004,7 @@ keywords: syscall wait4 The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in - microseconds, the pid, the executable name in paretheses, the + microseconds, the pid, the executable name in parentheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1". @@ -1020,7 +1020,7 @@ keywords: syscall read write time io number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in - parenthesese. The first line with the "access" keyword lists the file + parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write diff --git a/testsuite/systemtap.examples/memory/mmreclaim.meta b/testsuite/systemtap.examples/memory/mmreclaim.meta index c3b9cfc6..c301d302 100644 --- a/testsuite/systemtap.examples/memory/mmreclaim.meta +++ b/testsuite/systemtap.examples/memory/mmreclaim.meta @@ -8,7 +8,7 @@ status: experimental exit: user-controlled output: sorted-list scope: system-wide -description: The mmreclaim.stp script uses the virtual memory tracepoints available in some kernels to track page reclaim activity that occured while the script was running. Its useful is debugging performance problems that occur due to page reclamation. +description: The mmreclaim.stp script uses the virtual memory tracepoints available in some kernels to track page reclaim activity that occurred while the script was running. Its useful is debugging performance problems that occur due to page reclamation. test_support: stap -l kernel.trace("mm_directreclaim_reclaimall"),kernel.trace("mm_pagereclaim_shrinkinactive"),kernel.trace("mm_pagereclaim_free"),kernel.trace("mm_pagereclaim_pgout"),kernel.trace("mm_pagereclaim_shrinkactive_a2a"),kernel.trace("mm_pagereclaim_shrinkinactive_i2a"),kernel.trace("mm_pagereclaim_shrinkactive_a2i"),kernel.trace("mm_pagereclaim_shrinkinactive_i2i") test_check: stap -p4 mmreclaim.stp test_installcheck: stap mmreclaim.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/memory/mmwriteback.meta b/testsuite/systemtap.examples/memory/mmwriteback.meta index 1ad4947c..dbcaa476 100644 --- a/testsuite/systemtap.examples/memory/mmwriteback.meta +++ b/testsuite/systemtap.examples/memory/mmwriteback.meta @@ -8,7 +8,7 @@ status: experimental exit: user-controlled output: sorted-list scope: system-wide -description: The mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a supposedly idle system that is experiencing upexpected IO. +description: The mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a supposedly idle system that is experiencing unexpected IO. test_support: stap -l kernel.trace("mm_pdflush_bgwriteout"),kernel.trace("mm_pdflush_kupdate"),kernel.trace("mm_pagereclaim_pgout") test_check: stap -p4 mmwriteback.stp test_installcheck: stap mmwriteback.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/memory/numa_faults.meta b/testsuite/systemtap.examples/memory/numa_faults.meta index 51da3fc7..afd95e07 100644 --- a/testsuite/systemtap.examples/memory/numa_faults.meta +++ b/testsuite/systemtap.examples/memory/numa_faults.meta @@ -8,6 +8,6 @@ status: production exit: user-controlled output: list scope: system-wide -description: The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also providea a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer. +description: The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer. test_check: stap -p4 numa_faults.stp test_installcheck: stap numa_faults.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/memory/pfaults.meta b/testsuite/systemtap.examples/memory/pfaults.meta index 480e3b24..827e3816 100644 --- a/testsuite/systemtap.examples/memory/pfaults.meta +++ b/testsuite/systemtap.examples/memory/pfaults.meta @@ -8,6 +8,6 @@ status: production exit: user-controlled output: sorted-list scope: system-wide -description: The pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to determine where the page faults are occuring. +description: The pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to determine where the page faults are occurring. test_check: stap -p4 pfaults.stp test_installcheck: stap pfaults.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/network/netdev.stp b/testsuite/systemtap.examples/network/netdev.stp index 64c8167a..faf4d2ae 100755 --- a/testsuite/systemtap.examples/network/netdev.stp +++ b/testsuite/systemtap.examples/network/netdev.stp @@ -26,9 +26,9 @@ probe netdev.ioctl{ probe netdev.set_promiscuity { if (enable) - printf("Device %s entering in prosmicuous mode\n", dev_name) + printf("Device %s entering in promiscuous mode\n", dev_name) else - printf("Device %s leaving prosmicuous mode\n", dev_name) + printf("Device %s leaving promiscuous mode\n", dev_name) } probe netdev.change_rx_flag { @@ -41,7 +41,7 @@ probe netdev.change_mtu { } probe netdev.change_mac { - printf("Changing MAC adddres on device %s from %s to %s\n", + printf("Changing MAC address on device %s from %s to %s\n", dev_name, old_mac, new_mac) } diff --git a/testsuite/systemtap.examples/process/sigkill.meta b/testsuite/systemtap.examples/process/sigkill.meta index b0e04ce8..b9c83f15 100644 --- a/testsuite/systemtap.examples/process/sigkill.meta +++ b/testsuite/systemtap.examples/process/sigkill.meta @@ -8,7 +8,7 @@ status: production exit: user-controlled output: trace scope: systemwide -description: The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the desination executable and process ID, the executable name user ID that sent the signal. +description: The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the destination executable and process ID, the executable name user ID that sent the signal. arg_1: The name of the signal to look for on selected process. test_check: stap -p4 sigkill.stp test_installcheck: stap sigkill.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/process/sleeptime.meta b/testsuite/systemtap.examples/process/sleeptime.meta index 7318c7aa..e5aa4f35 100644 --- a/testsuite/systemtap.examples/process/sleeptime.meta +++ b/testsuite/systemtap.examples/process/sleeptime.meta @@ -8,6 +8,6 @@ status: production exit: user-controlled output: trace scope: system-wide -description: 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. +description: 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 parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds. test_check: stap -p4 sleeptime.stp test_installcheck: stap sleeptime.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/process/syscalls_by_proc.meta b/testsuite/systemtap.examples/process/syscalls_by_proc.meta index 42668bc8..6bb6a650 100644 --- a/testsuite/systemtap.examples/process/syscalls_by_proc.meta +++ b/testsuite/systemtap.examples/process/syscalls_by_proc.meta @@ -8,6 +8,6 @@ status: production exit: user-controlled output: sorted-list on-exit scope: system-wide -description: The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each executable ordered from greates to least number of syscalls. +description: The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each executable ordered from greatest to least number of syscalls. test_check: stap -p4 syscalls_by_proc.stp test_installcheck: stap syscalls_by_proc.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/process/wait4time.meta b/testsuite/systemtap.examples/process/wait4time.meta index e798014b..a9c9089a 100644 --- a/testsuite/systemtap.examples/process/wait4time.meta +++ b/testsuite/systemtap.examples/process/wait4time.meta @@ -8,6 +8,6 @@ status: production exit: user-controlled output: trace scope: system-wide -description: The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in paretheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1". +description: The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in parentheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1". test_check: stap -p4 wait4time.stp test_installcheck: stap wait4time.stp -c "sleep 0.2" -- cgit From ac505f97f1e85d95c9fe2b0401a375c2c8cd1cb9 Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Wed, 16 Sep 2009 15:52:17 -0700 Subject: Add the badname.stp example This is a toy script I wrote a while back to demonstrate how SystemTap could be used to enforce filesystem naming rules. --- testsuite/systemtap.examples/general/badname.meta | 13 +++++++++++ testsuite/systemtap.examples/general/badname.stp | 28 +++++++++++++++++++++++ testsuite/systemtap.examples/index.html | 3 +++ testsuite/systemtap.examples/index.txt | 7 ++++++ testsuite/systemtap.examples/keyword-index.html | 14 +++++++++++- testsuite/systemtap.examples/keyword-index.txt | 18 +++++++++++++++ 6 files changed, 82 insertions(+), 1 deletion(-) create mode 100644 testsuite/systemtap.examples/general/badname.meta create mode 100755 testsuite/systemtap.examples/general/badname.stp (limited to 'testsuite/systemtap.examples') diff --git a/testsuite/systemtap.examples/general/badname.meta b/testsuite/systemtap.examples/general/badname.meta new file mode 100644 index 00000000..9b4e7390 --- /dev/null +++ b/testsuite/systemtap.examples/general/badname.meta @@ -0,0 +1,13 @@ +title: Bad Filename Filter +name: badname.stp +version: 1.0 +keywords: filesystem hack +author: Josh Stone +subsystem: filesystem +status: experimental +exit: user-controlled +output: none +scope: system-wide +description: The badname.stp script shows how one could prevent the creation of files with undesirable names. +test_check: stap -p4 badname.stp +test_installcheck: stap badname.stp -c "sleep 0.2" diff --git a/testsuite/systemtap.examples/general/badname.stp b/testsuite/systemtap.examples/general/badname.stp new file mode 100755 index 00000000..153e08c5 --- /dev/null +++ b/testsuite/systemtap.examples/general/badname.stp @@ -0,0 +1,28 @@ +#!/usr/bin/stap -g +# badname.stp +# Prevent the creation of files with undesirable names. +# Source: http://blog.cuviper.com/2009/04/08/hacking-linux-filenames/ + +# return non-zero if the filename should be blocked +function filter:long (name:string) +{ + return euid() && isinstr(name, "XXX") +} + +global squash_inode_permission +probe kernel.function("may_create@fs/namei.c") +{ + # screen out the conditions which may_create will fail anyway + if ($child->d_inode || $dir->i_flags & 16) next + + # check that the new file meets our naming rules + if (filter(kernel_string($child->d_name->name))) + squash_inode_permission[tid()] = 1 +} +probe kernel.function("inode_permission@fs/namei.c").return !, + kernel.function("permission@fs/namei.c").return +{ + if (!$return && squash_inode_permission[tid()]) + $return = -13 # -EACCES (Permission denied) + delete squash_inode_permission[tid()] +} diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html index 203bc5d4..cd2faadb 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -46,6 +46,9 @@ keywords: FORMAT
        • general/ansi_colors2.stp - Show Attribues in Table for ansi_set_color3()
          keywords: FORMAT

          The script prints a table showing the available attributes (bold, underline, and inverse) with color combinations for the ans_set_color3() function in the ansi.stp tapset.

          • +
        • general/badname.stp - Bad Filename Filter
          +keywords: FILESYSTEM HACK
          +

          The badname.stp script shows how one could prevent the creation of files with undesirable names.

        • general/graphs.stp - Graphing Disk and CPU Utilization
          keywords: DISK CPU USE GRAPH

          The script tracks the disk and CPU utilization. The resulting output of the script can be piped into gnuplot to generate a graph of disk and CPU USE.

          • diff --git a/testsuite/systemtap.examples/index.txt b/testsuite/systemtap.examples/index.txt index 20b4da4f..2e096ab1 100644 --- a/testsuite/systemtap.examples/index.txt +++ b/testsuite/systemtap.examples/index.txt @@ -17,6 +17,13 @@ keywords: format ans_set_color3() function in the ansi.stp tapset. +general/badname.stp - Bad Filename Filter +keywords: filesystem hack + + The badname.stp script shows how one could prevent the creation of + files with undesirable names. + + general/graphs.stp - Graphing Disk and CPU Utilization keywords: disk cpu use graph diff --git a/testsuite/systemtap.examples/keyword-index.html b/testsuite/systemtap.examples/keyword-index.html index b59ce4a8..fe8fcc4e 100644 --- a/testsuite/systemtap.examples/keyword-index.html +++ b/testsuite/systemtap.examples/keyword-index.html @@ -39,7 +39,7 @@

        Examples by Keyword

        -

        AUTOFS BACKTRACE BUFFER CALLGRAPH CPU DEVICE DISK FORMAT FREE FUNCTIONS FUTEX GRAPH INTERRUPT IO LOCKING MEMORY MONITOR NETWORK NFS NUMA PER-PROCESS PROCESS PROFILING READ SCHEDULER SCSI SIGNALS SIMPLE SLEEP SOCKET STATISTICS SYSCALL TCP TIME TRACE TRACEPOINT TRAFFIC TTY USE WAIT4 WRITE

        +

        AUTOFS BACKTRACE BUFFER CALLGRAPH CPU DEVICE DISK FILESYSTEM FORMAT FREE FUNCTIONS FUTEX GRAPH HACK INTERRUPT IO LOCKING MEMORY MONITOR NETWORK NFS NUMA PER-PROCESS PROCESS PROFILING READ SCHEDULER SCSI SIGNALS SIMPLE SLEEP SOCKET STATISTICS SYSCALL TCP TIME TRACE TRACEPOINT TRAFFIC TTY USE WAIT4 WRITE

        AUTOFS

        • network/autofs4.stp - Watch autofs4 operations
          @@ -94,6 +94,12 @@ keywords: DISK DISK

          Get the status of reading/writing disk every 5 seconds, output top ten entries during that period.

        +

        FILESYSTEM

        +
          +
        • general/badname.stp - Bad Filename Filter
          +keywords: FILESYSTEM HACK
          +

          The badname.stp script shows how one could prevent the creation of files with undesirable names.

          • +

        FORMAT

        • general/ansi_colors.stp - Color Table for ansi_set_color2() and ansi_set_color3()
          @@ -127,6 +133,12 @@ keywords: SYSCALL DISK CPU USE GRAPH

          The script tracks the disk and CPU utilization. The resulting output of the script can be piped into gnuplot to generate a graph of disk and CPU USE.

        +

        HACK

        +
          +
        • general/badname.stp - Bad Filename Filter
          +keywords: FILESYSTEM HACK
          +

          The badname.stp script shows how one could prevent the creation of files with undesirable names.

          • +

        INTERRUPT

        • interrupt/scf.stp - Tally Backtraces for Inter-Processor Interrupt (IPI)
          diff --git a/testsuite/systemtap.examples/keyword-index.txt b/testsuite/systemtap.examples/keyword-index.txt index 81713991..866e1d86 100644 --- a/testsuite/systemtap.examples/keyword-index.txt +++ b/testsuite/systemtap.examples/keyword-index.txt @@ -106,6 +106,15 @@ keywords: disk ten entries during that period. += FILESYSTEM = + +general/badname.stp - Bad Filename Filter +keywords: filesystem hack + + The badname.stp script shows how one could prevent the creation of + files with undesirable names. + + = FORMAT = general/ansi_colors.stp - Color Table for ansi_set_color2() and ansi_set_color3() @@ -166,6 +175,15 @@ keywords: disk cpu use graph and CPU USE. += HACK = + +general/badname.stp - Bad Filename Filter +keywords: filesystem hack + + The badname.stp script shows how one could prevent the creation of + files with undesirable names. + + = INTERRUPT = interrupt/scf.stp - Tally Backtraces for Inter-Processor Interrupt (IPI) -- cgit From 15a53fb7e8f0e3eb7cc2476d390da7f8a06d2c5f Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Thu, 17 Sep 2009 15:30:56 +0200 Subject: Mark badname example as needing guru mode in meta file so it doesn't FAIL. --- testsuite/systemtap.examples/general/badname.meta | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'testsuite/systemtap.examples') diff --git a/testsuite/systemtap.examples/general/badname.meta b/testsuite/systemtap.examples/general/badname.meta index 9b4e7390..9a01763c 100644 --- a/testsuite/systemtap.examples/general/badname.meta +++ b/testsuite/systemtap.examples/general/badname.meta @@ -8,6 +8,6 @@ status: experimental exit: user-controlled output: none scope: system-wide -description: The badname.stp script shows how one could prevent the creation of files with undesirable names. -test_check: stap -p4 badname.stp -test_installcheck: stap badname.stp -c "sleep 0.2" +description: The badname.stp script shows how one could prevent the creation of files with undesirable names using guru mode. +test_check: stap -g -p4 badname.stp +test_installcheck: stap -g badname.stp -c "sleep 0.2" -- cgit From 6287a9e628bcbe6192da8fd9f0ce659a8acc13fc Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Thu, 17 Sep 2009 15:44:52 +0200 Subject: Regenerate examples index. --- testsuite/systemtap.examples/index.html | 2 +- testsuite/systemtap.examples/index.txt | 2 +- testsuite/systemtap.examples/keyword-index.html | 4 ++-- testsuite/systemtap.examples/keyword-index.txt | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) (limited to 'testsuite/systemtap.examples') diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html index cd2faadb..ba0d0fd7 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -48,7 +48,7 @@ keywords: FORMAT

          The script prints a table showing the available attributes (bold, underline, and inverse) with color combinations for the ans_set_color3() function in the ansi.stp tapset.

        • general/badname.stp - Bad Filename Filter
          keywords: FILESYSTEM HACK
          -

          The badname.stp script shows how one could prevent the creation of files with undesirable names.

          • +

          The badname.stp script shows how one could prevent the creation of files with undesirable names using guru mode.

        • general/graphs.stp - Graphing Disk and CPU Utilization
          keywords: DISK CPU USE GRAPH

          The script tracks the disk and CPU utilization. The resulting output of the script can be piped into gnuplot to generate a graph of disk and CPU USE.

          • diff --git a/testsuite/systemtap.examples/index.txt b/testsuite/systemtap.examples/index.txt index 2e096ab1..3d0495f5 100644 --- a/testsuite/systemtap.examples/index.txt +++ b/testsuite/systemtap.examples/index.txt @@ -21,7 +21,7 @@ general/badname.stp - Bad Filename Filter keywords: filesystem hack The badname.stp script shows how one could prevent the creation of - files with undesirable names. + files with undesirable names using guru mode. general/graphs.stp - Graphing Disk and CPU Utilization diff --git a/testsuite/systemtap.examples/keyword-index.html b/testsuite/systemtap.examples/keyword-index.html index fe8fcc4e..1a68a9f0 100644 --- a/testsuite/systemtap.examples/keyword-index.html +++ b/testsuite/systemtap.examples/keyword-index.html @@ -98,7 +98,7 @@ keywords: DISK
          • general/badname.stp - Bad Filename Filter
            keywords: FILESYSTEM HACK
            -

            The badname.stp script shows how one could prevent the creation of files with undesirable names.

            • +

            The badname.stp script shows how one could prevent the creation of files with undesirable names using guru mode.

          FORMAT

            @@ -137,7 +137,7 @@ keywords: DISK general/badname.stp - Bad Filename Filter
            keywords: FILESYSTEM HACK
            -

            The badname.stp script shows how one could prevent the creation of files with undesirable names.

            +

            The badname.stp script shows how one could prevent the creation of files with undesirable names using guru mode.

          INTERRUPT

            diff --git a/testsuite/systemtap.examples/keyword-index.txt b/testsuite/systemtap.examples/keyword-index.txt index 866e1d86..056b553a 100644 --- a/testsuite/systemtap.examples/keyword-index.txt +++ b/testsuite/systemtap.examples/keyword-index.txt @@ -112,7 +112,7 @@ general/badname.stp - Bad Filename Filter keywords: filesystem hack The badname.stp script shows how one could prevent the creation of - files with undesirable names. + files with undesirable names using guru mode. = FORMAT = @@ -181,7 +181,7 @@ general/badname.stp - Bad Filename Filter keywords: filesystem hack The badname.stp script shows how one could prevent the creation of - files with undesirable names. + files with undesirable names using guru mode. = INTERRUPT = -- cgit