Manpages

NAME

stappaths - systemtap configurable file paths

DESCRIPTION

This manual page was generated for systemtap 5.1. The following section will list the main paths in systemtap that are important to know and may be required to reference.
/usr/share/systemtap/tapset/

The directory for the standard probe-alias / function tapset library, unless overridden by the SYSTEMTAP_TAPSET environment variable or the XDG_DATA_DIRS environment variable. These are described in the stapprobes(3stap), probe::*(3stap), and function::*(3stap) manual pages.

/usr/share/systemtap/runtime/

The runtime sources, unless overridden by the SYSTEMTAP_RUNTIME environment variable.

/usr/bin/staprun

The auxiliary program supervising module loading, interaction, and unloading.

/etc/stap-exporter

The default directory to search for *.stp files, for exporting to HTTP.

/usr/lib/systemtap/stapio

The auxiliary program for module input and output handling.

/usr/include/sys/sdt.h

Location of the <sys/sdt.h> headers.

Kernel debuginfo Path: /usr/lib/debug/lib/modules/$(uname -r)/

The location of kernel debugging information when packaged into the kernel-debuginfo RPM, unless overridden by the SYSTEMTAP_DEBUGINFO_PATH environment variable. The default value for this variable is +:.debug:/usr/lib/debug:build. elfutils searches vmlinux in this path and it interprets the path as a base directory of which various subdirectories will be searched for finding debuginfo for the kernel, kernel modules, and user-space binaries. By default, systemtap will also look for vmlinux in these locations:

/boot/vmlinux-’uname -r’
/lib/modules/’uname -r’/vmlinux
/lib/modules/’uname -r’/vmlinux.debug
/lib/modules/’uname -r’/build/vmlinux
/lib/modules/’uname -r’/.debug/vmlinux.debug
/usr/lib/debug/lib/modules/’uname -r’/vmlinux.debug
/var/cache/abrt-di/usr/debug/lib/modules/’uname -r’/
/var/cache/abrt-di/usr/lib/debug/lib/modules/’uname -r’/vmlinux.debug

Corresponding source files are usually located under /usr/src/debug/. Further file information on user-space applications can be determined per-basis using rpm -ql <package>-debuginfo. For supported user-space applications information please visit the systemtap wiki.

With elfutils version >0.178, systemtap can automatically download debugging information from debuginfod servers. You can try it by setting an environment variable or two:
export DEBUGINFOD_URLS=https://debuginfod.elfutils.org/
export DEBUGINFOD_PROGRESS=1

$HOME/.systemtap

Systemtap data directory for cached systemtap files, unless overridden by the SYSTEMTAP_DIR environment variable.

/tmp/stapXXXXXX

Temporary directory for systemtap files, including translated C code and kernel object.

/lib/modules/VERSION/build

The location of kernel module building infrastructure.

/usr/share/doc/systemtap*/examples

Examples with greater detail can be found here. Each example comes with a .txt or .meta file explaining what the example, sample or demo does and how it is ordinarily run. See also online at: https://sourceware.org/systemtap/examples/

$SYSTEMTAP_DIR/ssl/server

User’s server-side SSL certificate database. If SYSTEMTAP_DIR is not set, the default is $HOME/.systemtap.

$SYSTEMTAP_DIR/ssl/client

User’s private client-side SSL certificate database. If SYSTEMTAP_DIR is not set, the default is $HOME/.systemtap.

/etc/systemtap/ssl/client

Global client-side SSL certificate database.

/etc/systemtap/staprun/

staprun's trusted signer certificate database.

/etc/sysconfig/stap-server

stap-server service global configuration file.

/etc/sysconfig/stap-exporter

stap-exporter service global configuration file.

/var/run/stap-server/

stap-server service default location of status files for running servers.

/var/log/stap-server/log

stap-server service default log file.

SEE ALSO

stapprobes(3stap),
staprun(8),
stapvars(3stap),
stapex(3stap),
stap-server(8),
awk(1),
gdb(1)
http://sourceware.org/elfutils/Debuginfod.html