Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #646
Difficulty: Easy
Apple Computer acquired NeXT on February 4, 1997, for $929 million USD.
True or False?
Linux & Unix Commands - Search Man Pages

trsp(8c) [bsd man page]

TRSP(8c)																  TRSP(8c)

trsp - transliterate sequenced packet protocol trace SYNOPSIS
trsp [ -a ] [ -s ] [ -t ] [ -j ] [ -p hex-address ] [ system [ core ] ] DESCRIPTION
Trpt interrogates the buffer of SPP trace records created when a socket is marked for "debugging" (see setsockopt(2)), and prints a read- able description of these records. When no options are supplied, trsp prints all the trace records found in the system grouped according to SPP connection protocol control block (PCB). The following options may be used to alter this behavior. -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, -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 who's address follows, -a in addition to the normal output, print the values of the source and destination addresses for each packet recorded. The recommended use of trsp 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 trsp with the -p option, supplying the associated protocol control block addresses. If there are many sockets using the debugging option, the -j option may be use- ful in checking to see if any trace records are present for the socket in question. 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. FILES
/vmunix /dev/kmem SEE ALSO
setsockopt(2), netstat(1) DIAGNOSTICS
``no namelist'' when the system image doesn't contain the proper symbols to find the trace buffer; others which should be self explanatory. BUGS
Should also print the data for each input or output, but this is not saved in the race record. The output format is inscrutable and should be described here. 4.2 Berkeley Distribution October 8, 1985 TRSP(8c)

Check Out this Related Man Page

trace(1)						      General Commands Manual							  trace(1)

       trace - trace system calls of programs

       trace [options] cmd args...

       The  command  with  no flag arguments traces for the given cmd and args all system calls made and prints a time stamp, the PID, call and/or
       return values and arguments and puts its output in the file trace.dump.

       -f filename
	       Puts dump in file filename.

       -z      Echos arguments only.

       Only one of the following option arguments can be specified at one time.

       -c#     Traces given PIDs and their children.  Up to sixteen PIDs can be specified.

       -g#     Traces given groups only.  Up to sixteen Group IDs can be specified.

       -p#     Traces given PIDs only.	Up to sixteen PIDs can be specified.

       -s#     Traces given system calls only.	Up to sixteen PIDs can be specified.

       -u#     Traces given UIDs only.	Up to sixteen PIDs can be specified.

       trace -f ls.dump ls -l /dev >ls.out
       runs the cmd ls -l /dev and puts the trace in ls.dump and output in ls.out.
       trace -f csh.trace -p $$ &
       will trace your login shell in the background. To stop the trace just send it a termination signal (that is, kill -TERM trace_pid).

       Due to security, no one, not even the super-user can trace anyone else's programs. This sort of negates some of the usefulness  of  the	-g
       and -u flags.

       The program cannot be traced.

       Only 16 numbers can be given to the -c, -p, -g, -u, and -s flags.

       The kernel configuration file must contain the following:
       options	       SYS_TRACE
       pseudo-device   sys_trace

       In addition, the superuser must use the following command sequence to create the device:
       cd /dev
       MAKEDEV trace
       If both lines are not in the configuration file or if the device is not made, the message "Cannot open /dev/trace" appears.

       /dev/trace     read only character special device for reading syscall data.

       trace.dump     default file for the system call trace data.

See Also
       open(2), close(2), ioctl(2), select(2), read(2), trace(5)


Featured Tech Videos