10.2;trpt , revision 2.0, 89/03/30 trpt -transliterate protocol trace usage: trpt [-a] [-c] [-a <PCB addr>] [-e] [-f] [-j] [-l] [-m] [-s] [-t] [-u] [-w] [-p <PCB addr>] [<filename>] DESCRIPTION trpt interrogates the buffer of TCP trace records created when a socket is marked for "debugging" (see setsockopt), 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 Print the values of the source and destination addresses for each packet recorded, in addition to the normal output. -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 <PCB addr> Show only trace records associated with the protocol control block, the address of which follows. -s Print a detailed description of the packet sequencing information, in addition to the normal output. (Currently unimplemented) -t Print the values for all timers at each point in the trace, in addition to the normal output. (Currently unimplemented) Domain/OS Aegis EXTENSIONS -c Clear trace buffer. -d <PCB addr> Toggle debug on a connection. -e Exit on a bad trace record. -l Print lapsed times, in addition to the normal output. -m Print output values, in decimal format. -u Print output values, in unsigned decimal format. -w Warn on bad trace records. NOTES 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. 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 file other than the default, which is `node_data/systmp/tcp_data, <filename> may be used to specify another file. BUGS trpt should print the data for each input or output, but this is not saved in the trace record. The output format is inscrutable. FILES `node_data/systmp/tcp_data SEE ALSO setsockopt, netstat; Configuring and Managing TCP/IP.