NAME

socket − EXOS communications end point

DESCRIPTION

Sockets are special files that are used to maintain host data structures for an EXOS 8010 communications end point.  Opening a socket initializes the host data structures and the corresponding EXOS board data structures.  This process requires cooperation with the /dev/EXOS/admin device. 

ioctl calls implement any protocol specific operations.  A read or write to a socket device transfers data to and from a remote process. 

A large number of ioctl calls apply to sockets and have the general form

#include <sys/soioctl.h>
#include <net/route.h>
ioctl (s, code, arg)
PARAM *arg;

The definition of PARAM depends on the codes shown below. Results, if any, are returned in *arg.

Applicable codes are the following:

SIOCADDRTAdd routing table entry (PARAM : route; no result)
SIOCATMARKAt out-of-band mark?  (no argument; RESULT : short)
SIOCCHGTGRTChange routing table entry  (PARAM : route; no result)
SIOCDELRTDelete routing table entry  (PARAM : route; no result)
SIOCDONEShutdown read/write on socket  (PARAM : int; no result)
SIOCGKEEPInspect keep-alive  (no argument; RESULT : short)
SIOCGLINGERGet linger time  (no argument; RESULT : short)
SIOCGPGRPGet process group  (no argument; RESULT : short)
SIOCRCVOOBGet out-of-band data  (no argument; RESULT : char)
SIOCSENDOOBSend out-of-band data  (PARAM : char; no result)
SIOCSKEEPSet keep-alive  (PARAM : int; no result)
SIOCSLINGERSet linger time  (PARAM : int; no result)
SIOCSPGRPSet process group  (PARAM : int; no result)

route is defined as struct rtentry route. 

SEE ALSO

socket(3N), accept(3N), connect(3N), receive(3N), send(3N), errlog(7), inet(7P), tcp(7P), udp(7P), and the Berkeley 4.2BSD documents
socket(2), route(1M)
A 4.2bsd Interprocess Communication Primer

FILES

/dev/EXOS/admin
/dev/EXOS/socket*

Version 2.4  —  September 29, 2021