trace-cmd-check-events(1) [centos man page]

TRACE-CMD-CHECK_EV(1)													     TRACE-CMD-CHECK_EV(1)

NAME

       trace-cmd-check-events - parse the event formats on local system

SYNOPSIS

       trace-cmd check-events [OPTIONS]

DESCRIPTION

       The trace-cmd(1) check-events parses format strings for all the events on the local system. It returns whether all the format strings can
       be parsed correctly. It will load plugins unless specified otherwise.

       This is useful to check for any trace event format strings which may contain some internal kernel function references which cannot be
       decoded outside of the kernel. This may mean that either the unparsed format strings of the trace events need to be changed or that a
       plugin needs to be created to parse them.

OPTIONS

       -N - Don't load plugins

SEE ALSO

       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), trace-cmd-start(1)

AUTHOR

       Written by Vaibhav Nagarnaik, <vnagarnaik@google.com[1]>

RESOURCES

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

COPYING

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

NOTES

	1. vnagarnaik@google.com
	   mailto:vnagarnaik@google.com

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

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

NAME

       trace-cmd - interacts with Ftrace Linux kernel internal tracer

SYNOPSIS

       trace-cmd COMMAND [OPTIONS]

DESCRIPTION

       The trace-cmd(1) command interacts with the Ftrace tracer that is built inside the Linux kernel. It interfaces with the Ftrace specific
       files found in the debugfs file system under the tracing directory. A COMMAND must be specified to tell trace-cmd what to do.

COMMANDS

	   record  - record a live trace and write a trace.dat file to the
		     local disk or to the network.

	   report  - reads a trace.dat file and converts the binary data to a
		     ASCII text readable format.

	   hist    - show a histogram of the events.

	   options - list the plugin options that are available to *report*

	   start   - start the tracing without recording to a trace.dat file.

	   stop    - stop tracing (only disables recording, overhead of tracer
		     is still in effect)

	   extract - extract the data from the kernel buffer and create a trace.dat
		     file.

	   reset   - disables all tracing and gives back the system performance.
		     (clears all data from the kernel buffers)

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

	   list    - list the available plugins or events that can be recorded.

	   listen  - open up a port to listen for remote tracing connections.

	   restore - restore the data files of a crashed run of trace-cmd record

	   stack   - run and display the stack tracer

	   check-events - parse format strings for all trace events and return
			  whether all formats are parseable

OPTIONS

       -h, --help
	   Display the help text.

       Other options see the man page for the corresponding command.

SEE ALSO

       trace-cmd-record(1), trace-cmd-report(1), trace-cmd-hist(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1),
       trace-cmd-reset(1), trace-cmd-restore(1), trace-cmd-stack(1), trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1), trace-cmd.dat(5),
       trace-cmd-check-events(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(1)