1reset-trace(8)              System Manager's Manual             reset-trace(8)
2
3
4

NAME

6       reset-trace - reset the state of tracing.
7

SYNOPSIS

9       reset-trace [-F] [-h] [-q] [-v]
10

DESCRIPTION

12       You will probably never need this tool. If you kill -9 a bcc tool (plus
13       other signals, like SIGTERM), or if a bcc  tool  crashes,  then  kernel
14       tracing  can  be  left  in  a semi-enabled state. It's not as bad as it
15       sounds: there may just be overhead for writing to ring buffers that are
16       never  read.  This  tool can be used to clean up the tracing state, and
17       reset and disable active tracing.
18
19       Make sure no other tracing sessions are active. This  tool  might  stop
20       them from functioning (perhaps ungracefully).
21
22       This  specifically  clears the state in at least the following files in
23       /sys/kernel/debug/tracing:  kprobe_events,  uprobe_events,  trace_pipe.
24       Other  tracing  facilities  (ftrace)  are  checked,  and  if  not in an
25       expected state, a note is printed. All tracing files can be reset  with
26       -F  for  force,  but this will interfere with any other running tracing
27       sessions (eg, ftrace).
28

REQUIREMENTS

30       /sys/kernel/debug mounted as debugfs
31

OPTIONS

33       -F     Force. Will reset all tracing facilities,  including  those  not
34              used by bcc (ftrace). You shouldn't need to use this.
35
36       -h     USAGE message.
37
38       -q     Quiet. No output while working.
39
40       -v     Verbose: print what it is doing.
41

EXAMPLES

43       Reset the state of tracing:
44              # reset-trace
45
46       Verbose:
47              # reset-trace -v
48
49
50       SOURCE
51              This is from bcc.
52
53              https://github.com/iovisor/bcc
54
55       Also  look  in  the bcc distribution for a companion _examples.txt file
56       containing example usage, output, and commentary for this tool.
57

OS

59       Linux
60

STABILITY

62       Unstable - in development.
63

AUTHOR

65       Brendan Gregg
66
67
68
69USER COMMANDS                     2016-10-18                    reset-trace(8)
Impressum