trace-cmd-start man page

trace-cmd-start — start the Ftrace Linux kernel tracer without recording

Synopsis

trace-cmd start [Options]

Description

The trace-cmd(1) start enables all the Ftrace tracing the same way trace-cmd-record(1) does. The difference is that it does not run threads to create a trace.dat file. This is useful just to enable Ftrace and you are only interested in the trace after some event has occurred and the trace is stopped. Then the trace can be read straight from the Ftrace pseudo file system or can be extracted with trace-cmd-extract(1).

Options

The options are the same as trace-cmd-record(1), except that it does not take options specific to recording (-s, -o, -F, -N, and -t).

See Also

trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1), trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1)

Author

Written by Steven Rostedt, <rostedt@goodmis.org[1]>

Resources

git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git

Copying

Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).

Notes

1.

rostedt@goodmis.org

mailto:rostedt@goodmis.org

Referenced By

trace-cmd(1), trace-cmd-check-events(1), trace-cmd.dat(5), trace-cmd-extract(1), trace-cmd-hist(1), trace-cmd-list(1), trace-cmd-listen(1), trace-cmd-mem(1), trace-cmd-options(1), trace-cmd-profile(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-reset(1), trace-cmd-restore(1), trace-cmd-show(1), trace-cmd-snapshot(1), trace-cmd-split(1), trace-cmd-stack(1), trace-cmd-stat(1), trace-cmd-stop(1), trace-cmd-stream(1).

10/19/2016