trace-cmd-start(1) — Linux manual page

TRACE-CMD-START(1)                                    TRACE-CMD-START(1)

NAME         top

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

SYNOPSIS         top

       trace-cmd start [OPTIONS]

DESCRIPTION         top

       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         top

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

       --fork
           This option is only available for trace-cmd start. It tells
           trace-cmd to not wait for the process to finish before
           returning. With this option, trace-cmd start will return
           right after it forks the process on the command line. This
           option only has an effect if trace-cmd start also executes a
           command.

SEE ALSO         top

       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         top

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

RESOURCES         top

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

COPYING         top

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

NOTES         top

        1. rostedt@goodmis.org
           mailto:rostedt@goodmis.org

COLOPHON         top

       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 man-pages@man7.org] If you have a
       bug report for this manual page, send it to Steven Rostedt
       <rostedt@goodmis.org>.  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 2021-08-27.  (At that time, the date of the most recent commit
       that was found in the repository was 2021-08-20.)  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 man-pages@man7.org

                               06/09/2020             TRACE-CMD-START(1)

Pages that refer to this page: trace-cmd(1),  trace-cmd-check-events(1),  trace-cmd-clear(1),  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-set(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),  trace-cmd.dat(5)

HTML rendering created 2022-12-18 by Michael Kerrisk, author of The Linux Programming Interface, maintainer of the Linux man-pages project. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH.