Commit | Line | Data |
---|---|---|
79be0566 KM |
1 | .\" Copyright (c) 1983 Regents of the University of California. |
2 | .\" All rights reserved. The Berkeley software License Agreement | |
3 | .\" specifies the terms and conditions for redistribution. | |
4 | .\" | |
5 | .\" @(#)trpt.8 5.1 (Berkeley) %G% | |
6 | .\" | |
7 | .TH TRPT 8C "2 March 1983" | |
8 | .UC 5 | |
9 | .SH NAME | |
10 | trpt \- transliterate protocol trace | |
11 | .SH SYNOPSIS | |
12 | .B trpt | |
13 | [ | |
14 | .B \-a | |
15 | ] [ | |
16 | .B \-s | |
17 | ] [ | |
18 | .B \-t | |
19 | ] [ | |
20 | .B \-j | |
21 | ] [ | |
22 | .B \-p | |
23 | hex-address ] | |
24 | [ system [ core ] ] | |
25 | .SH DESCRIPTION | |
26 | .I Trpt | |
27 | interrogates the buffer of TCP trace records created | |
28 | when a socket is marked for \*(lqdebugging\*(rq (see | |
29 | .IR setsockopt (2)), | |
30 | and prints a readable description of these records. | |
31 | When no options are supplied, | |
32 | .I trpt | |
33 | prints all the trace records found in the system | |
34 | grouped according to TCP connection protocol control | |
35 | block (PCB). The following options may be used to | |
36 | alter this behavior. | |
37 | .TP | |
38 | .B \-s | |
39 | in addition to the normal output, | |
40 | print a detailed description of the packet | |
41 | sequencing information, | |
42 | .TP | |
43 | .B \-t | |
44 | in addition to the normal output, | |
45 | print the values for all timers at each | |
46 | point in the trace, | |
47 | .TP | |
48 | .B \-j | |
49 | just give a list of the protocol control block | |
50 | addresses for which there are trace records, | |
51 | .TP | |
52 | .B \-p | |
53 | show only trace records associated with the protocol | |
54 | control block who's address follows, | |
55 | .TP | |
56 | .B \-a | |
57 | in addition to the normal output, | |
58 | print the values of the source and destination | |
59 | addresses for each packet recorded. | |
60 | .PP | |
61 | The recommended use of | |
62 | .I trpt | |
63 | is as follows. | |
64 | Isolate the problem and enable debugging on the | |
65 | socket(s) involved in the connection. | |
66 | Find the address of the protocol control blocks | |
67 | associated with the sockets using the | |
68 | .B \-A | |
69 | option to | |
70 | .IR netstat (1). | |
71 | Then run | |
72 | .I trpt | |
73 | with the | |
74 | .B \-p | |
75 | option, supplying the associated | |
76 | protocol control block addresses. If there are | |
77 | many sockets using the debugging option, the | |
78 | .B \-j | |
79 | option may be useful in checking to see if | |
80 | any trace records are present for the socket in | |
81 | question. | |
82 | .PP | |
83 | If debugging is being performed on a system or | |
84 | core file other than the default, the last two | |
85 | arguments may be used to supplant the defaults. | |
86 | .SH FILES | |
87 | /vmunix | |
88 | .br | |
89 | /dev/kmem | |
90 | .SH "SEE ALSO" | |
91 | setsockopt(2), netstat(1) | |
92 | .SH DIAGNOSTICS | |
93 | ``no namelist'' when the system image doesn't | |
94 | contain the proper symbols to find the trace buffer; | |
95 | others which should be self explanatory. | |
96 | .SH BUGS | |
97 | Should also print the data for each input or output, | |
98 | but this is not saved in the race record. | |
99 | .PP | |
100 | The output format is inscrutable and should be described | |
101 | here. |