trace-cmd-start - start the Ftrace Linux kernel tracer without recording
trace-cmd start [OPTIONS]
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).
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).
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)
Written by Steven Rostedt, <email@example.com>
Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).
1. firstname.lastname@example.org mailto:email@example.com
This page is part of the trace-cmd (a front-end for Ftrace) project. Information about the project can be found at [unknown -- if you know, please contact firstname.lastname@example.org] If you have a bug report for this manual page, send it to Steven Rostedt <email@example.com>. This page was obtained from the project's upstream Git repository ⟨git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git⟩ on 2017-04-25. If you discover any rendering problems in this HTML version of the page, or you believe there is a better or more up-to- date source for the page, or you have corrections or improvements to the information in this COLOPHON (which is not part of the original manual page), send a mail to firstname.lastname@example.org 01/25/2014 TRACE-CMD-START(1)
Pages that refer to this page: trace-cmd-extract(1), trace-cmd-stop(1)