Added xten to list of directories
[unix-history] / usr.sbin / trpt / trpt.8
CommitLineData
15637ed4
RG
1.\" Copyright (c) 1983, 1991 The Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\" must display the following acknowledgement:
14.\" This product includes software developed by the University of
15.\" California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)trpt.8 6.5 (Berkeley) 3/16/91
33.\"
34.Dd March 16, 1991
35.Dt TRPT 8
36.Os BSD 4.2
37.Sh NAME
38.Nm trpt
39.Nd transliterate protocol trace
40.Sh SYNOPSIS
41.Nm trpt
42.Op Fl a
43.Op Fl f
44.Op Fl j
45.Op Fl p Ar hex-address
46.Op Fl s
47.Op Fl t
48.Oo
49.Ar system Op Ar core
50.Oc
51.Sh DESCRIPTION
52.Nm Trpt
53interrogates the buffer of
54.Tn TCP
55trace records created
56when a socket is marked for
57.Dq debugging
58(see
59.Xr setsockopt 2 ) ,
60and prints a readable description of these records.
61When no options are supplied,
62.Nm trpt
63prints all the trace records found in the system
64grouped according to
65.Tn TCP
66connection protocol control
67block
68.Pq Tn PCB .
69The following options may be used to
70alter this behavior.
71.Bl -tag -width Ds
72.It Fl a
73In addition to the normal output,
74print the values of the source and destination
75addresses for each packet recorded.
76.It Fl f
77Follow the trace as it occurs, waiting a short time for additional records
78each time the end of the log is reached.
79.It Fl j
80Just give a list of the protocol control block
81addresses for which there are trace records.
82.It Fl p
83Show only trace records associated with the protocol
84control block at the given address
85.Ar hex-address .
86.It Fl s
87In addition to the normal output,
88print a detailed description of the packet
89sequencing information.
90.It Fl t
91in addition to the normal output,
92print the values for all timers at each
93point in the trace.
94.El
95.Pp
96The recommended use of
97.Nm trpt
98is as follows.
99Isolate the problem and enable debugging on the
100socket(s) involved in the connection.
101Find the address of the protocol control blocks
102associated with the sockets using the
103.Fl A
104option to
105.Xr netstat 1 .
106Then run
107.Nm trpt
108with the
109.Fl p
110option, supplying the associated
111protocol control block addresses.
112The
113.Fl f
114option can be used to follow the trace log once the trace is located.
115If there are
116many sockets using the debugging option, the
117.Fl j
118option may be useful in checking to see if
119any trace records are present for the socket in
120question.
121The
122.Pp
123If debugging is being performed on a system or
124core file other than the default, the last two
125arguments may be used to supplant the defaults.
126.Sh FILES
127.Bl -tag -width /dev/kmem -compact
3fcd7be6 128.It Pa /386bsd
15637ed4
RG
129.It Pa /dev/kmem
130.El
131.Sh SEE ALSO
132.Xr netstat 1 ,
133.Xr setsockopt 2 ,
134.Xr trsp 8
135.Sh DIAGNOSTICS
136.Bl -tag -width Ds
137.It Sy no namelist
138When the system image doesn't
139contain the proper symbols to find the trace buffer;
140others which should be self explanatory.
141.El
142.Sh BUGS
143Should also print the data for each input or output,
144but this is not saved in the race record.
145.Pp
146The output format is inscrutable and should be described
147here.
148.Sh HISTORY
149The
150.Nm
151command appeared in
152.Bx 4.2 .