This manual page documents a tool used for debugging failures in
the Xerox NS Sequenced packet protocol layer. It is adapted from
the Internet equivalent trpt(8c).
.\" Copyright (c) 1985, 1991 The Regents of the University of California.
.\" %sccs.include.redist.man%
.\" @(#)trsp.8 6.4 (Berkeley) %G%
.Nd transliterate sequenced packet protocol trace
interrogates the buffer of
when a socket is marked for
and prints a readable description of these records.
When no options are supplied,
prints all the trace records found in the system
connection protocol control
The following options may be used to
In addition to the normal output,
print the values of the source and destination
addresses for each packet recorded.
Just give a list of the protocol control block
addresses for which there are trace records.
Show only trace records associated with the protocol
control block at the given address,
in addition to the normal output,
print a detailed description of the packet
in addition to the normal output,
print the values for all timers at each
Isolate the problem and enable debugging on the
socket(s) involved in the connection.
Find the address of the protocol control blocks
associated with the sockets using the
option, supplying the associated
protocol control block addresses. If there are
many sockets using the debugging option, the
option may be useful in checking to see if
any trace records are present for the socket in
If debugging is being performed on a system or
core file other than the default, the last two
arguments may be used to supplant the defaults.
.Bl -tag -width /dev/kmem -compact
When the system image doesn't
contain the proper symbols to find the trace buffer;
others which should be self explanatory.
Should also print the data for each input or output,
but this is not saved in the race record.
The output format is inscrutable and should be described
projects / unix-history / blob