From 6f2e08530c527a072732d1792a092231d881647c Mon Sep 17 00:00:00 2001 From: ddomingo Date: Tue, 27 Jan 2009 14:40:18 +1000 Subject: minimized RHEL-isms in doc source, still need to edit and when building for non-RHEL though --- doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml | 2 +- doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml | 6 +++++- doc/SystemTap_Beginners_Guide/en-US/Introduction.xml | 4 +++- 3 files changed, 9 insertions(+), 3 deletions(-) (limited to 'doc/SystemTap_Beginners_Guide/en-US') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml b/doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml index 676af712..4d81c745 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml @@ -3,7 +3,7 @@ ]> - Red Hat Enterprise Linux Documentation + Red Hat, Inc. Don Domingo diff --git a/doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml b/doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml index 1599dc53..b8eba008 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml @@ -7,10 +7,14 @@ Introduction to SystemTap (for Red Hat Enterprise Linux 5.3) Introduction to SystemTap (for Fedora Core 10) 2.0 + Red Hat Enterprise Linux 5 + 2 - This guide provides basic instructions on how to use SystemTap to monitor different subsystems of &PRODUCT; in finer detail. The SystemTap Beginners Guide is recommended for users who have taken RHCT or have a similar level of expertise in &PRODUCT;. + This guide provides basic instructions on how to use SystemTap to monitor different subsystems of &PRODUCT; in finer detail. The SystemTap Beginners Guide is recommended for users who have taken RHCT or have a similar level of expertise in &PRODUCT;. + + This guide provides basic instructions on how to use SystemTap to monitor different subsystems of Fedora Core 10 in finer detail. The SystemTap Beginners Guide is recommended for users who have taken RHCT or have a similar level of expertise in Fedora Core 10. diff --git a/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml b/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml index 005bfba0..afb9e738 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml @@ -101,7 +101,9 @@ capabilities of SystemTap Introduction - SystemTap was originally developed to provide functionality for ∏ similar to previous Linux probing tools such as dprobes and the Linux Trace Toolkit. SystemTap aims to supplement the existing suite of Linux monitoring tools by providing users with the infrastructure to track kernel activity. In addition, SystemTap combines this capability with two things: +SystemTap was originally developed to provide functionality for ∏ similar to previous Linux probing tools such as dprobes and the Linux Trace Toolkit. SystemTap aims to supplement the existing suite of Linux monitoring tools by providing users with the infrastructure to track kernel activity. In addition, SystemTap combines this capability with two things: + +SystemTap was originally developed to provide functionality for Fedora Core 10 similar to previous Linux probing tools such as dprobes and the Linux Trace Toolkit. SystemTap aims to supplement the existing suite of Linux monitoring tools by providing users with the infrastructure to track kernel activity. In addition, SystemTap combines this capability with two things: -- cgit From 0404e375bc0b780c7cbf0f08a7a37a43de35eb02 Mon Sep 17 00:00:00 2001 From: ddomingo Date: Wed, 11 Feb 2009 10:51:13 +1000 Subject: corrected author name --- doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'doc/SystemTap_Beginners_Guide/en-US') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml b/doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml index 4d81c745..0c55a7ee 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Author_Group.xml @@ -13,4 +13,14 @@ ddomingo@redhat.com + + + William + Cohen + + Engineering Services and Operations + Performance Tools + + wcohen@redhat.com + -- cgit From 098043c5f96ee58756342cfbe7b49c2572f79a15 Mon Sep 17 00:00:00 2001 From: ddomingo Date: Wed, 11 Feb 2009 10:52:28 +1000 Subject: added section on how to monitor polling (testsuite/profiling/timeout.stp) --- .../en-US/Useful_Scripts-timeout.xml | 137 +++++++++++++++++++++ .../en-US/Useful_SystemTap_Scripts.xml | 1 + 2 files changed, 138 insertions(+) create mode 100644 doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-timeout.xml (limited to 'doc/SystemTap_Beginners_Guide/en-US') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-timeout.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-timeout.xml new file mode 100644 index 00000000..32ce8319 --- /dev/null +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-timeout.xml @@ -0,0 +1,137 @@ + + + + +
+Monitoring Polling Applications + +script examples +monitoring polling applications + + + +examples of SystemTap scripts +monitoring polling applications + + + +monitoring polling applications +examples of SystemTap scripts + + + + + +polling applications, monitoring +examples of SystemTap scripts + + + +uses systemtap/testsuite/systemtap.examples/profiling/timeout.stp + + + + + This section how to identify and monitor which applications are polling. Doing so allows you to track + unnecessary or excessive polling, which can help you pinpoint areas for improvement in terms of CPU usage + and power savings. + + + + timeout.stp + + + + + + + + + tracks how many times each application used the following system calls over time: + + + + poll + select + epoll + itimer + futex + nanosleep + signal + + + + In some applications, these system calls are used excessively. For example, an application that + needs to perform a task once every hour could be configured (or even designed) to check the + clock every second if the hour has already passed. Such design idioms are throwbacks to earlier + kernel versions, which used a periodic tick. + + + + +script examples +timer.s(), sample usage + + + +examples of SystemTap scripts +timer.s(), sample usage + + + +timer.s(), sample usage +examples of SystemTap scripts + + + + You can increase the sample time by editing the timer in the second probe (timer.s()). + The output of contains the name and UID of the top 20 polling applications, + along with how many times each application performed each polling system call (over time). + contains an excerpt of the script: + + + + <xref linkend="timeouts"/> Sample Output + + uid | poll select epoll itimer futex nanosle signal| process +28937 | 148793 0 0 4727 37288 0 0| firefox +22945 | 0 56949 0 1 0 0 0| scim-bridge + 0 | 0 0 0 36414 0 0 0| swapper + 4275 | 23140 0 0 1 0 0 0| mixer_applet2 + 4191 | 0 14405 0 0 0 0 0| scim-launcher +22941 | 7908 1 0 62 0 0 0| gnome-terminal + 4261 | 0 0 0 2 0 7622 0| escd + 3695 | 0 0 0 0 0 7622 0| gdm-binary + 3483 | 0 7206 0 0 0 0 0| dhcdbd + 4189 | 6916 0 0 2 0 0 0| scim-panel-gtk + 1863 | 5767 0 0 0 0 0 0| iscsid + 2562 | 0 2881 0 1 0 1438 0| pcscd + 4257 | 4255 0 0 1 0 0 0| gnome-power-man + 4278 | 3876 0 0 60 0 0 0| multiload-apple + 4083 | 0 1331 0 1728 0 0 0| Xorg + 3921 | 1603 0 0 0 0 0 0| gam_server + 4248 | 1591 0 0 0 0 0 0| nm-applet + 3165 | 0 1441 0 0 0 0 0| xterm +29548 | 0 1440 0 0 0 0 0| httpd + 1862 | 0 0 0 0 0 1438 0| iscsid + + + + +
+ diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml index 8b7fc741..ed089361 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml @@ -62,6 +62,7 @@ + -- cgit From ccae4f38c9107f56b99bfc19ed01cea03d370576 Mon Sep 17 00:00:00 2001 From: ddomingo Date: Thu, 12 Feb 2009 11:36:55 +1000 Subject: added topsys.stp to examples (profiling) --- .../en-US/Useful_Scripts-timeout.xml | 23 ++-- .../en-US/Useful_Scripts-topsys.xml | 131 +++++++++++++++++++++ .../en-US/Useful_SystemTap_Scripts.xml | 1 + 3 files changed, 143 insertions(+), 12 deletions(-) create mode 100644 doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-topsys.xml (limited to 'doc/SystemTap_Beginners_Guide/en-US') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-timeout.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-timeout.xml index 32ce8319..719f5c6d 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-timeout.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-timeout.xml @@ -67,10 +67,11 @@ uses systemtap/testsuite/systemtap.examples/profiling/timeout.stp - In some applications, these system calls are used excessively. For example, an application that - needs to perform a task once every hour could be configured (or even designed) to check the - clock every second if the hour has already passed. Such design idioms are throwbacks to earlier - kernel versions, which used a periodic tick. + In some applications, these system calls are used excessively. As such, they are normally identified as "likely + culprits" for polling applications. Note, however, that an application may be using a different system + call to poll excessively; sometimes, it is useful to find out the top system calls used by the system (refer to + for instructions). Doing so can help you identify any additional suspects, which you + can add to for tracking. @@ -88,13 +89,6 @@ uses systemtap/testsuite/systemtap.examples/profiling/timeout.stp timer.s(), sample usage examples of SystemTap scripts - - - You can increase the sample time by editing the timer in the second probe (timer.s()). - The output of contains the name and UID of the top 20 polling applications, - along with how many times each application performed each polling system call (over time). - contains an excerpt of the script: - <xref linkend="timeouts"/> Sample Output @@ -132,6 +126,11 @@ foreach (fn+ in called) # Sort by function name printf("%s %d\n", fn, @count(called[fn])) exit() }--> - + + You can increase the sample time by editing the timer in the second probe (timer.s()). + The output of contains the name and UID of the top 20 polling applications, + along with how many times each application performed each polling system call (over time). + contains an excerpt of the script: + diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-topsys.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-topsys.xml new file mode 100644 index 00000000..700ef4ed --- /dev/null +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-topsys.xml @@ -0,0 +1,131 @@ + + + + +
+Tracking Most Frequently Used System Calls + +script examples +monitoring system calls + + + +examples of SystemTap scripts +monitoring system calls + + + +monitoring system calls +examples of SystemTap scripts + + + + + +system calls, monitoring +examples of SystemTap scripts + + + +uses systemtap/testsuite/systemtap.examples/profiling/topsys.stp + + + + + from helps you identify which applications + are polling by pointing out which ones used the following system calls most frequently: + + + + poll + select + epoll + itimer + futex + nanosleep + signal + + + + However, in some systems, a different system call might be responsible for excessive polling. If you suspect + that a polling application might is using a different system call to poll, you need to identify first the top + system calls used by the system. To do this, use . + + + + topsys.stp + + + + + + + + + lists the top 20 system calls used by the system per 5-second interval. It also lists + how many times each system call was used during that period. Refer to for a sample output. + + + +script examples +timer.s(), sample usage + + + +examples of SystemTap scripts +timer.s(), sample usage + + + +timer.s(), sample usage +examples of SystemTap scripts + + + + + <xref linkend="topsys"/> Sample Output + +-------------------------------------------------------------- + SYSCALL COUNT + gettimeofday 1857 + read 1821 + ioctl 1568 + poll 1033 + close 638 + open 503 + select 455 + write 391 + writev 335 + futex 303 + recvmsg 251 + socket 137 + clock_gettime 124 + rt_sigprocmask 121 + sendto 120 + setitimer 106 + stat 90 + time 81 + sigreturn 72 + fstat 66 +-------------------------------------------------------------- + + + + +
+ diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml index ed089361..c2c83a82 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml @@ -63,6 +63,7 @@ + -- cgit From ea5bbf556d840b1e0d49c33fd106b9462fada542 Mon Sep 17 00:00:00 2001 From: ddomingo Date: Wed, 18 Feb 2009 10:18:07 +1000 Subject: added legal notice to override Publican default, doc source is now GPL2 --- doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml | 2 +- .../en-US/Legal_Notice.xml | 30 ++++++++++++++++++++++ 2 files changed, 31 insertions(+), 1 deletion(-) create mode 100644 doc/SystemTap_Beginners_Guide/en-US/Legal_Notice.xml (limited to 'doc/SystemTap_Beginners_Guide/en-US') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml b/doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml index b8eba008..07c3f74d 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml @@ -27,7 +27,7 @@ &YEAR; &HOLDER; - + diff --git a/doc/SystemTap_Beginners_Guide/en-US/Legal_Notice.xml b/doc/SystemTap_Beginners_Guide/en-US/Legal_Notice.xml new file mode 100644 index 00000000..1fcb7b99 --- /dev/null +++ b/doc/SystemTap_Beginners_Guide/en-US/Legal_Notice.xml @@ -0,0 +1,30 @@ + + + + + + This documentation is free software; you can redistribute + it and/or modify it under the terms of the GNU General Public + License version 2 as published by the Free Software Foundation. + + + + This program is distributed in the hope that it will be + useful, but WITHOUT ANY WARRANTY; without even the implied + warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. + See the GNU General Public License for more details. + + + + You should have received a copy of the GNU General Public + License along with this program; if not, write to the Free + Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, + MA 02111-1307 USA + + + + For more details see the file COPYING in the source + distribution of Linux. + + -- cgit From 912907c362c919c33802104c0cd04c467c3e64cc Mon Sep 17 00:00:00 2001 From: ddomingo Date: Wed, 18 Feb 2009 12:26:48 +1000 Subject: 485491, revised installation instructions, now uses yum install and debuginfo-install for kernel info pkgs --- .../en-US/Installation.xml | 145 ++++++++++----------- 1 file changed, 67 insertions(+), 78 deletions(-) (limited to 'doc/SystemTap_Beginners_Guide/en-US') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Installation.xml b/doc/SystemTap_Beginners_Guide/en-US/Installation.xml index 3a45d269..d0ce1f26 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Installation.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Installation.xml @@ -70,7 +70,7 @@ systemtap-runtime - Assuming that your system is configured to use Red Hat Network (RHN) or yum is available, these two rpms can be installed with yum install systemtap systemtap-runtime. Note that before you can use SystemTap, you will still need to install the required kernel information RPMs. + Assuming that yum is installed in the system, these two rpms can be installed with yum install systemtap systemtap-runtime. Note that before you can use SystemTap, you will still need to install the required kernel information RPMs. @@ -99,9 +99,12 @@ kernel information packages - SystemTap needs information about the kernel in order to place instrumentation in it (i.e. probe it). This information also allows SystemTap to generate the code for the instrumentation. This information is contained in the matching -devel and -debuginfo packages for your kernel. The necessary -devel and - -debuginfo packages for the ordinary "vanilla" kernel - are as follows: + + SystemTap needs information about the kernel in order to place instrumentation in it (i.e. probe it). This + information also allows SystemTap to generate the code for the instrumentation. This information is contained + in the matching -devel, -debuginfo, and -debuginfo-common + packages for your kernel. The necessary -devel and -debuginfo packages for the ordinary + "vanilla" kernel are as follows: @@ -137,7 +140,9 @@ uname -r - For example, if you wish to use SystemTap on kernel version 2.6.18-53.el5 on an i686 machine, then you would need to download and install the following RPMs: + + For example, if you wish to use SystemTap on kernel version 2.6.18-53.el5 on an i686 machine, then you would + need to download and install the following RPMs: @@ -146,92 +151,75 @@ uname -r kernel-devel-2.6.18-53.1.13.el5.i686.rpm - + Important - The version, variant, and architecture of the -devel, -debuginfo and -debuginfo-common packages must match the kernel you wish to probe with SystemTap exactly. + The version, variant, and architecture of the -devel, -debuginfo and + -debuginfo-common packages must match the kernel you wish to probe with SystemTap exactly. + + + + The easiest way to install the required kernel information packages is through yum install + and debuginfo-install. debuginfo-install is included with later versions of the + yum-utils package (for example, version 1.1.10), and also requires an appropriate yum + repository from which to download and install -debuginfo/-debuginfo-common packages. + + + + Most of the required kernel packages can be found at + . Configure + yum accordingly by adding a new "debug" yum repository file + under /etc/yum.repos.d containing the following lines: + + + +[fedora-debuginfo] +name=Fedora $releasever - $basearch - Debug +failovermethod=priority +baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/debug/ +enabled=1 + + + + + Most required kernel packages can be found at + ; navigate there until you find the + appropriate Debuginfo directory for your system. Configure + yum accordingly by adding a new "debug" yum repository file under + /etc/yum.repos.d containing the following lines: + + +[rhel-debuginfo] +name=Red Hat Enterprise Linux $releasever - $basearch - Debug +baseurl=ftp://ftp.redhat.com/pub/redhat/linux/enterprise/$releasever/en/os/$basearch/Debuginfo/ +enabled=1 + - To help ease your deployment of SystemTap, you can use . - determines the kernel information packages you need to install in order - to run SystemTap. If you run (as an ordinary, non-root user) without - any arguments, it will display the kernel information packages required for the - loaded kernel. You can also pass a specific kernel version to - (e.g. 2.6.18-92.el5) if you wish - to probe a kernel that is not currently loaded. + After configuring yum with the appropriate repository, you can now install + the required -devel, -debuginfo, and -debuginfo-common + packages for your kernel. To install the corresponding packages for a specific kernel, run the following commands: - - Installation - stapprep.sh - - - stapprep.sh - + +yum install kernelname-devel-version +debuginfo-install kernelname-version + - - - - - Installation - installation script - - - - installation script - - - Note - Running as root will display the required kernel packages and install them as well, provided that yum and yum-utils are configured properly. - - - In order for yum to find and download the required kernel packages, you need to - point it to a repository containing those packages. Most required kernel packages can be found at - ; navigate there until you find the - appropriate Debuginfo directory for your system. Configure - yum accordingly by adding a new "debug" yum repository file under /etc/yum.repos.d containing the following lines: - - - -[rhel-debuginfo] -name=Red Hat Enterprise Linux $releasever - $basearch - Debug -baseurl=ftp://ftp.redhat.com/pub/redhat/linux/enterprise/$releasever/en/os/$basearch/Debuginfo/ -enabled=1 - - - - - - -script for installing kernel information packages - - -stapprep.sh - - - - + Replace kernelname with the appropriate kernel variant name + (for example, kernel-PAE), and version + with the target kernel's version. For example, to install the required kernel information packages for + the kernel-PAE--2.6.18-53.1.13.el5 kernel, run: - - - + + yum install kernel-PAE-devel-2.6.18-53.1.13.el5 + debuginfo-install kernel-PAE-2.6.18-53.1.13.el5 + If you do not have yum and yum-utils installed (and you are unable to install them), you will have to manually download and install the required kernel information packages. To generate the URL from which to download the required packages, use the following script: @@ -280,6 +268,7 @@ Once you have manually downloaded the required packages to the machine, install +
Initial Testing -- cgit From e9156044d841db08161c7f0f505d5f47ae8d2b9f Mon Sep 17 00:00:00 2001 From: ddomingo Date: Fri, 20 Feb 2009 15:59:01 +1000 Subject: added Tracking System Call Volume Per Process section --- .../en-US/Useful_Scripts-syscallsbyprocpid.xml | 132 +++++++++++++++++++++ .../en-US/Useful_SystemTap_Scripts.xml | 1 + 2 files changed, 133 insertions(+) create mode 100644 doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-syscallsbyprocpid.xml (limited to 'doc/SystemTap_Beginners_Guide/en-US') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-syscallsbyprocpid.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-syscallsbyprocpid.xml new file mode 100644 index 00000000..d8fe4b39 --- /dev/null +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-syscallsbyprocpid.xml @@ -0,0 +1,132 @@ + + + + +
+Tracking System Call Volume Per Process + +script examples +monitoring system calls (volume per process) + + + +examples of SystemTap scripts +monitoring system calls (volume per process) + + + +monitoring system calls (volume per process) +examples of SystemTap scripts + + + + + +system calls volume (per process), monitoring +examples of SystemTap scripts + + + +uses systemtap/testsuite/systemtap.examples/process/syscalls_by_p*.stp + + + + This section illustrates how to determine which processes + are performing the highest volume of system calls. In + previous sections, we've described how to monitor the top system + calls used by the system over time (). + We've also described how to identify which applications use a + specific set of "polling suspect" system calls the most + (). Monitoring the volume of + system calls made by each process provides more data in + investigating your system for polling processes and other resource + hogs. + + + + syscalls_by_proc.stp + + + + + + + + + lists the top 20 processes performing the + highest number of system calls. It also lists how many system calls each process + performed during the time period. Refer to + for a sample output. + + + + + <xref linkend="topsys"/> Sample Output + +Collecting data... Type Ctrl-C to exit and display results +#SysCalls Process Name +1577 multiload-apple +692 synergyc +408 pcscd +376 mixer_applet2 +299 gnome-terminal +293 Xorg +206 scim-panel-gtk +95 gnome-power-man +90 artsd +85 dhcdbd +84 scim-bridge +78 gnome-screensav +66 scim-launcher +[...] + + + + + If you prefer the output to display the process IDs instead of the process names, + use the following script instead. + + + + syscalls_by_pid.stp + + + + + + + + + + As indicated in the output, you need to manually exit the script in order to display the + results. You can add a timed expiration to either script by simply adding + a timer.s() probe; for example, to instruct the script to expire after + 5 seconds, add the following probe to the script: + + + +probe timer.s(5) +{ + exit() +} + + + + +
+ diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml index c2c83a82..b18062f3 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_SystemTap_Scripts.xml @@ -64,6 +64,7 @@ +
-- cgit