Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

trpt(8) [freebsd man page]

TRPT(8) 						    BSD System Manager's Manual 						   TRPT(8)

NAME

     trpt -- transliterate protocol trace

SYNOPSIS

     trpt [-a] [-f] [-j] [-p hex-address] [-s] [-t] [system [core]]

DESCRIPTION

     The trpt utility interrogates the buffer of TCP trace records created when a socket is marked for ``debugging'' (see setsockopt(2)), 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:

     -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.

     -p      Show only trace records associated with the protocol control block at the given address hex-address.

     -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.

     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(1).  Then run trpt with the -p option, sup-
     plying 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

     /boot/kernel/kernel
     /dev/kmem

DIAGNOSTICS

     no namelist  When the system image does not contain the proper symbols to find the trace buffer; others which should be self explanatory.

SEE ALSO

     netstat(1), setsockopt(2)

HISTORY

     The trpt utility appeared in 4.2BSD.

BUGS

     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.

BSD
								 December 11, 1993							       BSD

Check Out this Related Man Page

TRSP(8c)																  TRSP(8c)

NAME

       trsp - transliterate sequenced packet protocol trace

SYNOPSIS

       trsp [ -a ] [ -s ]  [ -t ] [ -j ] [ -p hex-address ] [ system [ core ] ]

DESCRIPTION

       Trpt  interrogates  the buffer of SPP trace records created when a socket is marked for "debugging" (see setsockopt(2)), and prints a read-
       able description of these records.  When no options are supplied, trsp prints all the trace records found in the system	grouped  according
       to SPP connection protocol control block (PCB).	The following options may be used to alter this behavior.

       -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,

       -j     just give a list of the protocol control block addresses for which there are trace records,

       -p     show only trace records associated with the protocol control block who's address follows,

       -a     in addition to the normal output, print the values of the source and destination addresses for each packet recorded.

       The recommended use of trsp 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(1).  Then run trsp with  the  -p  option,
       supplying the associated protocol control block addresses.  If there are many sockets using the debugging option, the -j option may be use-
       ful 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

       /vmunix
       /dev/kmem

SEE ALSO

       setsockopt(2), netstat(1)

DIAGNOSTICS

       ``no namelist'' when the system image doesn't contain the proper symbols to find the trace buffer; others which should be self explanatory.

BUGS

       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 here.

4.2 Berkeley Distribution					  October 8, 1985							  TRSP(8c)
Man Page