Search all pages
Professions, Sciences, Humanities, Business, ...
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Conversions, tests, processing, manipulation,...
Integer, Floating point, Matrix, Statistics, Boolean, ...
Algorithms, Memory, Process control, Debugging, ...
Data storage, Integrity, Encryption, Compression, ...
Networks, protocols, Interprocess, Remote, Client Server, ...
Timing, Calendar and Clock, Audio, Video, Printer, Controls...
Management, Filtering, File & Directory access, Viewers, ...
RocketLink!--> Man page versions:
TRSP(8) OpenBSD System Manager's Manual TRSP(8)
trsp - transliterate sequenced packet protocol trace
trsp [-a] [-j] [-p hex-address] [-s] [-t] [-z] [-N system] [-M core]
Trsp interrogates the buffer of SPP 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, trsp prints
all the trace records found in the system grouped according to SPP con-
nection 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.
-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.
-z Clear the in-kernel debugging buffers.
Extract values associated with the name list from core instead of
the default /dev/kmem.
Extract the name list from system instead of the default /bsd.
The recommended use of trsp is as follows. Isolate the problem and en-
able debugging on the socket(s) involved in the connection. Find the ad-
dress 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 sock-
ets 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.
/dev/kmem default kernel memory
/bsd default system namelist
netstat(1), setsockopt(2), trpt(8)
When the system image doesn't contain the proper symbols to find
the trace buffer; others which should be self explanatory.
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.
The trsp command appeared in 4.3BSD.
4.3 Berkeley Distribution June 6, 1993 2
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.
(Corrections, notes, and links courtesy of RocketAware.com)
OpenBSD sources for trsp(8)
Up to: Communication Debugging - Status, tracing, and debugging communications and protocols.
RocketLink!--> Man page versions:
Search | About | Comments | Submit Path: RocketAware > man pages >
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments