Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

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

NAME
trace-cmd-listen - listen for incoming connection to record tracing. SYNOPSIS
trace-cmd listen -p port [OPTIONS] DESCRIPTION
The trace-cmd(1) listen sets up a port to listen to waiting for connections from other hosts that run trace-cmd-record(1) with the -N option. When a connection is made, and the remote host sends data, it will create a file called trace.HOST:PORT.dat. Where HOST is the name of the remote host, and PORT is the port that the remote host used to connect with. OPTIONS
-p port This option will specify the port to listen to. -D This options causes trace-cmd listen to go into a daemon mode and run in the background. -d dir This option specifies a directory to write the data files into. -o filename This option overrides the default trace in the trace.HOST:PORT.dat that is created when a remote host connects. -l filename This option writes the output messages to a log file instead of standard output. 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-split(1), trace-cmd-list(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-LISTEN(1)

Check Out this Related Man Page

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

NAME
trace-cmd-extract - extract out the data from the Ftrace Linux tracer. SYNOPSIS
trace-cmd extract [OPTIONS] DESCRIPTION
The trace-cmd(1) extract is usually used after trace-cmd-start(1) and trace-cmd-stop(1). It can be used after the Ftrace tracer has been started manually through the Ftrace pseudo file system. The extract command creates a trace.dat file that can be used by trace-cmd-report(1) to read from. It reads the kernel internal ring buffer to produce the trace.dat file. OPTIONS
-p plugin Although extract does not start any traces, some of the plugins require just reading the output in ASCII format. These are the latency tracers, since the latency tracers have a separate internal buffer. The plugin option is therefore only necessary for the wakeup, wakeup-rt, irqsoff, preemptoff and preemptirqsoff plugins. With out this option, the extract command will extract from the internal Ftrace buffers. -O option If a latency tracer is being extracted, and the -p option is used, then there are some Ftrace options that can change the format. This will update those options before extracting. To see the list of options see trace-cmd-list. To enable an option, write its name, to disable the option append the characters no to it. For example: noprint-parent will disable the print-parent option that prints the parent function in printing a function event. -o outputfile By default, the extract command will create a trace.dat file. This option will change where the file is written to. SEE ALSO
trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(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 06/11/2014 TRACE-CMD-EXTRACT(1)
Man Page

Featured Tech Videos