1TRACE-CMD-START(1) libtracefs Manual TRACE-CMD-START(1)
2
3
4
6 trace-cmd-start - start the Ftrace Linux kernel tracer without
7 recording
8
10 trace-cmd start [OPTIONS]
11
13 The trace-cmd(1) start enables all the Ftrace tracing the same way
14 trace-cmd-record(1) does. The difference is that it does not run
15 threads to create a trace.dat file. This is useful just to enable
16 Ftrace and you are only interested in the trace after some event has
17 occurred and the trace is stopped. Then the trace can be read straight
18 from the Ftrace pseudo file system or can be extracted with
19 trace-cmd-extract(1).
20
22 The options are the same as trace-cmd-record(1), except that it does
23 not take options specific to recording (-s, -o, -N, and -t).
24
25 --fork
26 This option is only available for trace-cmd start. It tells
27 trace-cmd to not wait for the process to finish before returning.
28 With this option, trace-cmd start will return right after it forks
29 the process on the command line. This option only has an effect if
30 trace-cmd start also executes a command.
31
33 trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1),
34 trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1),
35 trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1)
36
38 Written by Steven Rostedt, <rostedt@goodmis.org[1]>
39
41 https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/
42
44 Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted
45 under the terms of the GNU Public License (GPL).
46
48 1. rostedt@goodmis.org
49 mailto:rostedt@goodmis.org
50
51
52
53libtracefs 10/11/2022 TRACE-CMD-START(1)