Print this page
NEX-9586 remove nodename from the default savecore directory path
Reviewed by: Dan Fields <dan.fields@nexenta.com>
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Reviewed by: Sanjay Nadkarni <sanjay.nadkarni@nexenta.com>
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man1/tnfxtract.1
+++ new/usr/src/man/man1/tnfxtract.1
1 1 '\" te
2 2 .\" Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved
3 +.\" Copyright 2017 Nexenta Systems, Inc. All Rights Reserved.
3 4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 -.TH TNFXTRACT 1 "Aug 19, 2003"
7 +.TH TNFXTRACT 1 "Feb 13, 2017"
7 8 .SH NAME
8 9 tnfxtract \- extract kernel probes output into a trace file
9 10 .SH SYNOPSIS
10 11 .LP
11 12 .nf
12 13 \fBtnfxtract\fR [\fB-d\fR \fIdumpfile\fR \fB-n\fR \fInamelist\fR] \fItnf_file\fR
13 14 .fi
14 15
15 16 .SH DESCRIPTION
16 -.sp
17 17 .LP
18 18 The \fBtnfxtract\fR utility collects kernel trace output from an in-core buffer
19 19 in the Solaris kernel, or from the memory image of a crashed system, and
20 20 generates a binary \fBTNF\fR trace file like those produced directly by user
21 21 programs being traced.
22 22 .sp
23 23 .LP
24 24 Either both or neither of the \fB-d\fR and \fB-n\fR options must be specified.
25 25 If neither is specified, trace output is extracted from the running kernel. If
26 26 both are specified, the \fB-d\fR argument names the file containing the
27 27 (crashed) system memory image, and the \fB-n\fR argument names the file
28 28 containing the symbol table for the system memory image.
29 29 .sp
30 30 .LP
31 31 The \fBTNF\fR trace file \fItnf_file\fR produced is exactly the same size as
32 32 the in-core buffer; it is essentially a snapshot of that buffer. It is legal
|
↓ open down ↓ |
6 lines elided |
↑ open up ↑ |
33 33 to run \fBtnfxtract\fR while kernel tracing is active, i.e., while the in-core
34 34 buffer is being written. \fBtnfxtract\fR insures that the output file it
35 35 generates is low-level consistent, that is, that only whole probes are written
36 36 out, and that internal data structures in the buffer are not corrupted because
37 37 the buffer is being concurrently written.
38 38 .sp
39 39 .LP
40 40 The \fBTNF\fR trace file generated is suitable as input to \fBtnfdump\fR(1),
41 41 which will generate an \fBASCII\fR file.
42 42 .SH OPTIONS
43 -.sp
44 43 .LP
45 44 The following options are supported:
46 45 .sp
47 46 .ne 2
48 47 .na
49 48 \fB\fB-d\fR \fIdumpfile\fR\fR
50 49 .ad
51 50 .RS 15n
52 51 Uses \fIdumpfile\fR as the system memory image, instead of the running kernel.
53 52 The \fIdumpfile\fR is normally the path name of a file generated by the
54 53 \fBsavecore\fR utility.
55 54 .RE
56 55
57 56 .sp
|
↓ open down ↓ |
4 lines elided |
↑ open up ↑ |
58 57 .ne 2
59 58 .na
60 59 \fB\fB-n\fR \fInamelist\fR\fR
61 60 .ad
62 61 .RS 15n
63 62 Uses \fInamelist\fR as the file containing the symbol table information for the
64 63 given \fIdumpfile\fR.
65 64 .RE
66 65
67 66 .SH OPERANDS
68 -.sp
69 67 .LP
70 68 The following operand is supported:
71 69 .sp
72 70 .ne 2
73 71 .na
74 72 \fB\fItnf_file\fR\fR
75 73 .ad
76 74 .RS 12n
77 75 Output file generated by \fBtnfxtract\fR based on kernel trace output from an
78 76 in-core buffer in the Solaris kernel.
79 77 .RE
80 78
81 79 .SH EXAMPLES
82 80 .LP
83 81 \fBExample 1 \fRExtracting probes from a running kernel
84 82 .sp
85 83 .LP
86 84 Extract probes from the running kernel into \fBktrace.out\fR:
87 85
88 86 .sp
89 87 .in +2
90 88 .nf
91 89 example% \fBtnfxtract ktrace.out\fR
92 90 .fi
93 91 .in -2
94 92 .sp
|
↓ open down ↓ |
16 lines elided |
↑ open up ↑ |
95 93
96 94 .LP
97 95 \fBExample 2 \fRExtracting probes from a kernel crash dump
98 96 .sp
99 97 .LP
100 98 Extract probes from a kernel crash dump into \fBktrace.out\fR:
101 99
102 100 .sp
103 101 .in +2
104 102 .nf
105 -example% \fBtnfxtract -d /var/crash/`uname -n`/vmcore.0 \e
106 - -n /var/crash/`uname -n`/unix.0 ktrace.out\fR
103 +example% \fBtnfxtract -d /var/crash/data/UUID/core.0 \e
104 + -n /var/crash/data/UUID/unix.0 ktrace.out\fR
107 105 .fi
108 106 .in -2
109 107 .sp
110 108
111 109 .SH EXIT STATUS
112 -.sp
113 110 .LP
114 111 The following exit values are returned:
115 112 .sp
116 113 .ne 2
117 114 .na
118 115 \fB\fB0\fR\fR
119 116 .ad
120 117 .RS 6n
121 118 Successful completion.
122 119 .RE
123 120
|
↓ open down ↓ |
1 lines elided |
↑ open up ↑ |
124 121 .sp
125 122 .ne 2
126 123 .na
127 124 \fB\fB>0\fR\fR
128 125 .ad
129 126 .RS 6n
130 127 An error occurred.
131 128 .RE
132 129
133 130 .SH SEE ALSO
134 -.sp
135 131 .LP
136 132 \fBprex\fR(1), \fBtnfdump\fR(1), \fBsavecore\fR(1M),
137 133 \fBtnf_kernel_probes\fR(4), \fBattributes\fR(5)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX