trace-cmd-reset(1) [centos man page]

TRACE-CMD-RESET(1)														TRACE-CMD-RESET(1)

NAME

       trace-cmd-reset - turn off all Ftrace tracing to bring back full performance

SYNOPSIS

       trace-cmd reset [OPTIONS]

DESCRIPTION

       The trace-cmd(1) reset command turns off all tracing of Ftrace. This will bring back the performance of the system before tracing was
       enabled. This is necessary since trace-cmd-record(1), trace-cmd-stop(1) and trace-cmd-extract(1) do not disable the tracer, event after the
       data has been pulled from the buffers. The rational is that the user may want to manually enable the tracer with the Ftrace pseudo file
       system, or examine other parts of Ftrace to see what trace-cmd did. After the reset command happens, the data in the ring buffer, and the
       options that were used are all lost.

OPTIONS

       -b buffer_size
	   When the kernel boots, the Ftrace ring buffer is of a minimal size (3 pages per CPU). The first time the tracer is used, the ring
	   buffer size expands to what it was set for (default 1.4 Megs per CPU).

	       If no more tracing is to be done, this option allows you to shrink the
	       ring buffer down to free up available memory.

	       trace-cmd reset -b 1

SEE ALSO

       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(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

								    06/11/2014							TRACE-CMD-RESET(1)

TRACE-CMD-SPLIT(1)														TRACE-CMD-SPLIT(1)

NAME

       trace-cmd-split - split a trace.dat file into smaller files

SYNOPSIS

       trace-cmd split [OPTIONS] [start-time [end-time]]

DESCRIPTION

       The trace-cmd(1) split is used to break up a trace.dat into small files. The start-time specifies where the new file will start at. Using
       trace-cmd-report(1) and copying the time stamp given at a particular event, can be used as input for either start-time or end-time. The
       split will stop creating files when it reaches an event after end-time. If only the end-time is needed, use 0.0 as the start-time.

       If start-time is left out, then the split will start at the beginning of the file. If end-time is left out, then split will continue to the
       end unless it meets one of the requirements specified by the options.

OPTIONS

       -i file
	   If this option is not specified, then the split command will look for the file named trace.dat. This options will allow the reading of
	   another file other than trace.dat.

       -o file
	   By default, the split command will use the input file name as a basis of where to write the split files. The output file will be the
	   input file with an attached '.#' to the end: trace.dat.1, trace.dat.2, etc.

	       This option will change the name of the base file used.

	       -o file	will create file.1, file.2, etc.

       -s seconds
	   This specifies how many seconds should be recorded before the new file should stop.

       -m milliseconds
	   This specifies how many milliseconds should be recorded before the new file should stop.

       -u microseconds
	   This specifies how many microseconds should be recorded before the new file should stop.

       -e events
	   This specifies how many events should be recorded before the new file should stop.

       -p pages
	   This specifies the number of pages that should be recorded before the new file should stop.

	       Note: only one of *-p*, *-e*, *-u*, *-m*, *-s* may be specified at a time.

	       If *-p* is specified, then *-c* is automatically set.

       -r
	   This option causes the break up to repeat until end-time is reached (or end of the input if end-time is not specified).

	       trace-cmd split -r -e 10000

	       This will break up trace.dat into several smaller files, each with at most
	       10,000 events in it.

       -c
	   This option causes the above break up to be per CPU.

	       trace-cmd split -c -p 10

	       This will create a file that has 10 pages per each CPU from the input.

SEE ALSO

       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(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

								    06/11/2014							TRACE-CMD-SPLIT(1)