|
|
1.1 root 1: .\" Copyright (c) 1983 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted provided
5: .\" that: (1) source distributions retain this entire copyright notice and
6: .\" comment, and (2) distributions including binaries display the following
7: .\" acknowledgement: ``This product includes software developed by the
8: .\" University of California, Berkeley and its contributors'' in the
9: .\" documentation or other materials provided with the distribution and in
10: .\" all advertising materials mentioning features or use of this software.
11: .\" Neither the name of the University nor the names of its contributors may
12: .\" be used to endorse or promote products derived from this software without
13: .\" specific prior written permission.
14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
17: .\"
18: .\" @(#)trpt.8 6.4 (Berkeley) 6/24/90
19: .\"
20: .TH TRPT 8 "June 24, 1990"
21: .UC 5
22: .SH NAME
23: trpt \- transliterate protocol trace
24: .SH SYNOPSIS
25: .B trpt
26: [
27: .B \-a
28: ] [
29: .B \-s
30: ] [
31: .B \-t
32: ] [
33: .B \-f
34: ] [
35: .B \-j
36: ] [
37: .B \-p
38: hex-address ]
39: [ system [ core ] ]
40: .SH DESCRIPTION
41: .I Trpt
42: interrogates the buffer of TCP trace records created
43: when a socket is marked for \*(lqdebugging\*(rq (see
44: .IR setsockopt (2)),
45: and prints a readable description of these records.
46: When no options are supplied,
47: .I trpt
48: prints all the trace records found in the system
49: grouped according to TCP connection protocol control
50: block (PCB). The following options may be used to
51: alter this behavior.
52: .TP
53: .B \-a
54: in addition to the normal output,
55: print the values of the source and destination
56: addresses for each packet recorded.
57: .TP
58: .B \-s
59: in addition to the normal output,
60: print a detailed description of the packet
61: sequencing information.
62: .TP
63: .B \-t
64: in addition to the normal output,
65: print the values for all timers at each
66: point in the trace.
67: .TP
68: .B \-f
69: follow the trace as it occurs, waiting a short time for additional records
70: each time the end of the log is reached.
71: .TP
72: .B \-j
73: just give a list of the protocol control block
74: addresses for which there are trace records.
75: .TP
76: .B \-p
77: show only trace records associated with the protocol
78: control block, the address of which follows.
79: .PP
80: The recommended use of
81: .I trpt
82: is as follows.
83: Isolate the problem and enable debugging on the
84: socket(s) involved in the connection.
85: Find the address of the protocol control blocks
86: associated with the sockets using the
87: .B \-A
88: option to
89: .IR netstat (1).
90: Then run
91: .I trpt
92: with the
93: .B \-p
94: option, supplying the associated
95: protocol control block addresses.
96: The
97: .B \-f
98: option can be used to follow the trace log once the trace is located.
99: If there are
100: many sockets using the debugging option, the
101: .B \-j
102: option may be useful in checking to see if
103: any trace records are present for the socket in
104: question.
105: The
106: .PP
107: If debugging is being performed on a system or
108: core file other than the default, the last two
109: arguments may be used to supplant the defaults.
110: .SH FILES
111: /vmunix
112: .br
113: /dev/kmem
114: .SH "SEE ALSO"
115: netstat(1), setsockopt(2), trsp(8)
116: .SH DIAGNOSTICS
117: ``no namelist'' when the system image doesn't
118: contain the proper symbols to find the trace buffer;
119: others which should be self explanatory.
120: .SH BUGS
121: Should also print the data for each input or output,
122: but this is not saved in the race record.
123: .PP
124: The output format is inscrutable and should be described
125: here.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.