macro and text revision (-mdoc version 3)
[unix-history] / usr / src / usr.sbin / trsp / trsp.8
CommitLineData
361f3820
KS
1This manual page documents a tool used for debugging failures in
2the Xerox NS Sequenced packet protocol layer. It is adapted from
3the Internet equivalent trpt(8c).
b42074ab 4.\" Copyright (c) 1985, 1991 The Regents of the University of California.
58bdc154 5.\" All rights reserved.
361f3820 6.\"
24f519df 7.\" %sccs.include.redist.man%
361f3820 8.\"
b42074ab 9.\" @(#)trsp.8 6.4 (Berkeley) %G%
58bdc154 10.\"
b42074ab
CL
11.Dd
12.Dt TRSP 8
13.Os BSD 4.2
14.Sh NAME
15.Nm trsp
16.Nd transliterate sequenced packet protocol trace
17.Sh SYNOPSIS
18.Nm trsp
19.Op Fl a
20.Op Fl s
21.Op Fl t
22.Op Fl j
23.Op Fl p Ar hex-address
24.Oo
25.Ar system Op Ar core
26.Oc
27.Sh DESCRIPTION
28.Xr Trpt
29interrogates the buffer of
30.Tn SPP
31trace records created
32when a socket is marked for
33.Dq debugging
34(see
35.Xr setsockopt 2 ) ,
361f3820
KS
36and prints a readable description of these records.
37When no options are supplied,
b42074ab 38.Nm trsp
361f3820 39prints all the trace records found in the system
b42074ab
CL
40grouped according to
41.Tn SPP
42connection protocol control
43block
44.Pq Tn PCB .
45The following options may be used to
361f3820 46alter this behavior.
b42074ab
CL
47.Bl -tag -width Ds
48.It Fl a
49In addition to the normal output,
50print the values of the source and destination
51addresses for each packet recorded.
52.It Fl j
53Just give a list of the protocol control block
54addresses for which there are trace records.
55.It Fl p
56Show only trace records associated with the protocol
57control block at the given address,
58.Ar hex-address .
59.It Fl s
361f3820
KS
60in addition to the normal output,
61print a detailed description of the packet
b42074ab
CL
62sequencing information.
63.It Fl t
361f3820
KS
64in addition to the normal output,
65print the values for all timers at each
66point in the trace,
b42074ab
CL
67.El
68.Pp
361f3820 69The recommended use of
b42074ab 70.Nm trsp
361f3820
KS
71is as follows.
72Isolate the problem and enable debugging on the
73socket(s) involved in the connection.
74Find the address of the protocol control blocks
75associated with the sockets using the
b42074ab 76.Fl A
361f3820 77option to
b42074ab 78.Xr netstat 1 .
361f3820 79Then run
b42074ab 80.Nm trsp
361f3820 81with the
b42074ab 82.Fl p
361f3820
KS
83option, supplying the associated
84protocol control block addresses. If there are
85many sockets using the debugging option, the
b42074ab 86.Fl j
361f3820
KS
87option may be useful in checking to see if
88any trace records are present for the socket in
89question.
b42074ab 90.Pp
361f3820
KS
91If debugging is being performed on a system or
92core file other than the default, the last two
93arguments may be used to supplant the defaults.
b42074ab
CL
94.Sh FILES
95.Bl -tag -width /dev/kmem -compact
96.It Pa /vmunix
97.It Pa /dev/kmem
98.El
99.Sh SEE ALSO
100.Xr netstat 1 ,
101.Xr setsockopt 2
102.Sh DIAGNOSTICS
103.Bl -tag -width Ds
104.It Sy no namelist
105When the system image doesn't
361f3820
KS
106contain the proper symbols to find the trace buffer;
107others which should be self explanatory.
b42074ab 108.Sh BUGS
361f3820
KS
109Should also print the data for each input or output,
110but this is not saved in the race record.
b42074ab 111.Pp
361f3820
KS
112The output format is inscrutable and should be described
113here.
b42074ab
CL
114.Sh HISTORY
115The
116.Nm
117command appeared in
118.Bx 4.3 .