Provided by: trace-cmd_1.0.3-0ubuntu2_i386 bug

NAME

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

SYNOPSIS

       trace-cmd stop

DESCRIPTION

       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.

SEE ALSO

       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

       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

                                  12/03/2011                 TRACE-CMD-STOP(1)