MirBSD manpage: trpt(8)

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


     trpt - transliterate protocol trace


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


     trpt 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 con-
     nection protocol control block (PCB).

     The options are as follows:

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

     -M core
             Extract values associated with the name list from core instead of
             the running kernel.

     -N system
             Extract the name list from system instead of the running kernel.

     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, supplying the as-
     sociated 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.


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


     netstat(1), setsockopt(2)


     The trpt command appeared in 4.2BSD.


     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.

MirBSD #10-current            December 11, 1993                              1

Generated on 2022-12-24 01:00:14 by $MirOS: src/scripts/roff2htm,v 1.113 2022/12/21 23:14:31 tg Exp $ — This product includes material provided by mirabilos.

These manual pages and other documentation are copyrighted by their respective writers; their sources are available at the project’s CVSweb, AnonCVS and other mirrors. The rest is Copyright © 2002–2022 MirBSD.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.

Kontakt / Impressum & Datenschutzerklärung