trpt(1M) UNIX System V(Internet Utilities) trpt(1M)
NAME
trpt - transliterate protocol trace
SYNOPSIS
trpt [ -afjst ] [ -p hex-address ] [ system [ core ] ]
DESCRIPTION
trpt interrogates the buffer of TCP trace records created when a socket
is marked for debugging [see getsockopt(3N)], and prints a readable
description of these records. When no options are supplied, trpt prints
all the trace records found in the system grouped according to TCP
connection protocol control block (PCB). The following options may be
used to alter this behavior.
OPTIONS
-a In addition to the normal output, print the values of the source
and destination addresses for each packet recorded.
-f Follow the trace as it occurs, waiting a short time for additional
records each time the end of the log is reached.
-j Just give a list of the protocol control block addresses for which
there are trace records.
-s In addition to the normal output, print a detailed description of
the packet sequencing information.
-t In addition to the normal output, print the values for all timers
at each point in the trace.
-p hex-address
Show only trace records associated with the protocol control block,
the address of which follows.
The recommended use of trpt is as follows. 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 -A option to netstat(1M). Then run trpt with the -p option,
supplying the associated protocol control block addresses. The -f option
can be used to follow the trace log once the trace is located. If there
are many sockets using the debugging option, the -j option may be useful
in checking to see if any trace records are present for the socket in
question.
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.
FILES
/stand/unix
/dev/kmem
10/89 Page 1
trpt(1M) UNIX System V(Internet Utilities) trpt(1M)
SEE ALSO
netstat(1M), getsockopt(3N)
DIAGNOSTICS
no namelist
When the system image does not contain the proper symbols to find
the trace buffer; others which should be self explanatory.
NOTES
Should also print the data for each input or output, but this is not
saved in the trace record.
The output format is inscrutable and should be described here.
Page 2 10/89