]>
Commit | Line | Data |
---|---|---|
013061cf EJ |
1 | .TH ovs\-parse\-backtrace 8 "October 2012" "Open vSwitch" "Open vSwitch Manual" |
2 | . | |
3 | .SH NAME | |
4 | ovs\-parse\-backtrace \- parses ovs-appctl backtrace output | |
5 | . | |
6 | .SH SYNOPSIS | |
7 | \fBovs\-appctl backtrace\fR | \fBovs\-parse\-backtrace\fR [\fIbinary\fR] | |
8 | .P | |
9 | \fBovs\-parse\-backtrace\fR [\fIbinary\fR] < \fIbacktrace\fR | |
10 | . | |
11 | .SH DESCRIPTION | |
12 | In some configurations, many Open vSwitch daemons can produce a series of | |
13 | backtraces using the \fBovs\-appctl backtrace\fR command. Users can analyze | |
14 | these backtraces to figure out what the given Open vSwitch daemon may be | |
15 | spending most of its time doing. \fBovs\-parse\-backtrace\fR makes this output | |
16 | easier to interpret. | |
17 | .PP | |
18 | The \fBovs\-appctl backtrace\fR output must be supplied on standard input. The | |
19 | binary that produced the output should be supplied as the sole non-option | |
20 | argument. For best results, the binary should have debug symbols. | |
21 | . | |
22 | .SH OPTIONS | |
23 | .TP | |
24 | \fB\-\-help\fR | |
25 | Prints a usage message and exits. | |
26 | .P | |
27 | \fB\-\-version\fR | |
28 | Prints the version and exits. |