|
|
1.1 ! root 1: .TH ISOC 1C "31 May 1988" ! 2: .\" $Header: /f/osi/support/RCS/isoc.1c,v 7.0 89/11/23 22:27:14 mrose Rel $ ! 3: .\" ! 4: .\" ! 5: .\" $Log: isoc.1c,v $ ! 6: .\" Revision 7.0 89/11/23 22:27:14 mrose ! 7: .\" Release 6.0 ! 8: .\" ! 9: .SH NAME ! 10: isoc \- minimal ISODE client for testing ! 11: .SH SYNOPSIS ! 12: .in +.5i ! 13: .ti -.5i ! 14: .B isoc ! 15: host provider entity ! 16: .in -.5i ! 17: .SH DESCRIPTION ! 18: The \fIisoc\fR program requests a few minimal ISODE services ! 19: and is useful primarily for debugging purposes. ! 20: Currently, ! 21: several entities can be requested, depending on the provider selected. ! 22: The echo entities will verify that the data they send is received correctly. ! 23: The \fIisode/\fR entities use association control (when applicable) ! 24: in order to test out these newer facilities. ! 25: .PP ! 26: Further, ! 27: to measure raw TCP performance, the \fIsink\fR entity can be requested of ! 28: the \fIraw\fR provider. ! 29: This option depends on the target system already having a TCP sink server in ! 30: place. ! 31: Berkeley UNIX sites usually have such a server. ! 32: .PP ! 33: To summarize: ! 34: .sp ! 35: .in +.5i ! 36: .nf ! 37: .ta \w'\fIprovider\fR 'u ! 38: \fIprovider\fR \fIentity\fR ! 39: raw sink ! 40: tsap echo, sink ! 41: ssap echo, sink ! 42: psap echo, sink, ! 43: isode/echo, isode/sink ! 44: rtsap echo, sink, ! 45: ros_echo, ros_sink, ! 46: \*(lqisode/rtse echo\*(rq, \*(rqisode/rtse sink\*(rq ! 47: isode/ros_echo, isode/ros_sink ! 48: rosap echo, sink, ! 49: isode/echo, isode/sink ! 50: .re ! 51: .fi ! 52: .in -.5i ! 53: .sp ! 54: .PP ! 55: Finally, ! 56: on those hosts with sub\-second timing facilities, ! 57: by redirecting \fIisoc\fR's standard input to a file, ! 58: raw performance at a given layer can be measured. ! 59: .SH FILES ! 60: .nf ! 61: .ta \w'\*(EDisoservices 'u ! 62: \*(EDisoservices ISODE services database ! 63: .re ! 64: .fi ! 65: .SH "SEE ALSO" ! 66: isoservices(5), isore(8c) ! 67: .SH AUTHOR ! 68: Marshall T. Rose
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.