Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ trpt(1M) — A/UX 2.0

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

getsockopt(2N)

netstat(1N)




trpt(1M) trpt(1M)
NAME trpt - transliterate protocol trace SYNOPSIS /usr/etc/trpt [-a] [-j] [-phex-address] [-s] [-t] [system[core]] DESCRIPTION trpt prints a readable description of TCP trace records created when a socket is marked for debugging (see getsockopt(2N)). When you don't supply an flag option, trpt prints all the trace records grouped according to TCP con- nection protocol control block (PCB). The following flag options alter this: -a in addition to the normal output, print the values of the source and destination addresses for each packet recorded -j list only the protocol control block addresses for which there are trace records -phex-address list only trace records associated with the hex- address protocol control block -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 system used for debugging a system other than the default core used for debugging a core file other than the de- fault We recommend the following use of trpt. Isolate the problem and enable debugging on the socket(s) involved in the con- nection. Find the address of the protocol control blocks associated with the sockets using netstat -A (see netstat(1N)). Then, run trpt -p and supply the associated protocol control block addresses. If there are many sockets using the debugging flag option, you might want to use the -j flag option to check for any trace records for the socket in question. FILES /usr/etc/trpt /unix /dev/kmem April, 1990 1



trpt(1M) trpt(1M)
SEE ALSO getsockopt(2N), netstat(1N). DIAGNOSTICS no namelist the system image doesn't contain the proper symbols to find the trace buffer. Other diagnostics are self explanatory. BUGS Should also print the data for each input or output, but this is not saved in the trace record. 2 April, 1990

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026