From 79be056636ec4575a1b18f1842fceb8f491b7867 Mon Sep 17 00:00:00 2001 From: Kirk McKusick Date: Sat, 27 Apr 1985 23:00:18 -0800 Subject: [PATCH] manual page first distributed with 4.2BSD SCCS-vsn: usr.sbin/trpt/trpt.8 5.1 --- usr/src/usr.sbin/trpt/trpt.8 | 101 +++++++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 usr/src/usr.sbin/trpt/trpt.8 diff --git a/usr/src/usr.sbin/trpt/trpt.8 b/usr/src/usr.sbin/trpt/trpt.8 new file mode 100644 index 0000000000..fa508c4f6a --- /dev/null +++ b/usr/src/usr.sbin/trpt/trpt.8 @@ -0,0 +1,101 @@ +.\" Copyright (c) 1983 Regents of the University of California. +.\" All rights reserved. The Berkeley software License Agreement +.\" specifies the terms and conditions for redistribution. +.\" +.\" @(#)trpt.8 5.1 (Berkeley) %G% +.\" +.TH TRPT 8C "2 March 1983" +.UC 5 +.SH NAME +trpt \- transliterate protocol trace +.SH SYNOPSIS +.B trpt +[ +.B \-a +] [ +.B \-s +] [ +.B \-t +] [ +.B \-j +] [ +.B \-p +hex-address ] +[ system [ core ] ] +.SH DESCRIPTION +.I Trpt +interrogates the buffer of TCP trace records created +when a socket is marked for \*(lqdebugging\*(rq (see +.IR setsockopt (2)), +and prints a readable description of these records. +When no options are supplied, +.I 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. +.TP +.B \-s +in addition to the normal output, +print a detailed description of the packet +sequencing information, +.TP +.B \-t +in addition to the normal output, +print the values for all timers at each +point in the trace, +.TP +.B \-j +just give a list of the protocol control block +addresses for which there are trace records, +.TP +.B \-p +show only trace records associated with the protocol +control block who's address follows, +.TP +.B \-a +in addition to the normal output, +print the values of the source and destination +addresses for each packet recorded. +.PP +The recommended use of +.I 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 +.B \-A +option to +.IR netstat (1). +Then run +.I trpt +with the +.B \-p +option, supplying the associated +protocol control block addresses. If there are +many sockets using the debugging option, the +.B \-j +option may be useful in checking to see if +any trace records are present for the socket in +question. +.PP +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. +.SH FILES +/vmunix +.br +/dev/kmem +.SH "SEE ALSO" +setsockopt(2), netstat(1) +.SH DIAGNOSTICS +``no namelist'' when the system image doesn't +contain the proper symbols to find the trace buffer; +others which should be self explanatory. +.SH BUGS +Should also print the data for each input or output, +but this is not saved in the race record. +.PP +The output format is inscrutable and should be described +here. -- 2.20.1