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

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | SEE ALSO | AUTHOR | RESOURCES | COPYING | NOTES | COLOPHON

TRACE-CMD-STOP(1)                                      TRACE-CMD-STOP(1)

NAME         top

       trace-cmd-stop - stop the Ftrace Linux kernel tracer from writing
       to the ring buffer.

SYNOPSIS         top

       trace-cmd stop [OPTIONS]

DESCRIPTION         top

       The trace-cmd(1) stop is a complement to trace-cmd-start(1). This
       will disable Ftrace from writing to the ring buffer. This does
       not stop the overhead that the tracing may incur. Only the
       updating of the ring buffer is disabled, the Ftrace tracing may
       still be inducing overhead.

       After stopping the trace, the trace-cmd-extract(1) may strip out
       the data from the ring buffer and create a trace.dat file. The
       Ftrace pseudo file system may also be examined.

       To disable the tracing completely to remove the overhead it
       causes, use trace-cmd-reset(1). But after a reset is performed,
       the data that has been recorded is lost.

OPTIONS         top

       -B buffer-name
           If the kernel supports multiple buffers, this will stop the
           trace for only the given buffer. It does not affect any other
           buffer. This may be used multiple times to specify different
           buffers. When this option is used, the top level instance
           will not be stopped unless -t is given.

       -a
           Stop the trace for all existing buffer instances. When this
           option is used, the top level instance will not be stopped
           unless -t is given.

       -t
           Stops the top level instance buffer. Without the -B or -a
           option this is the same as the default. But if -B or -a is
           used, this is required if the top level instance buffer
           should also be stopped.

SEE ALSO         top

       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1),
       trace-cmd-start(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-04-01.  (At that time, the date of the most recent commit
       that was found in the repository was 2021-03-26.)  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

                               05/27/2020              TRACE-CMD-STOP(1)

Pages that refer to this page: trace-cmd(1)trace-cmd-check-events(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-split(1)trace-cmd-start(1)trace-cmd-stat(1)trace-cmd-stream(1)trace-cmd.dat(5)