|
|
#include <sys/tiuser.h>int t_optmgmt (fd, req, ret) int fd; struct t_optmgmt *req; struct t_optmgmt *ret;
The req and ret
arguments point to a t_optmgmt
structure containing the following
members:
struct netbuf opt; long flags;The
opt
field identifies protocol options, and the
flags
field is used to specify the action to take with those options.
The options are represented by a netbuf
(see
netbuf(FP);
also for len
, buf
, and maxlen
)
structure in a manner similar to the address in t_bind.
req is used to request a specific action of the provider and to
send options to the provider.
len
specifies the number of bytes in the options,
buf
points to the options buffer, and
maxlen
has no meaning for the req argument.
The transport provider may return options and flag values
to the user through ret.
For ret, maxlen
specifies the maximum size of the options buffer and
buf
points to the buffer where the options are to be placed.
On return, len
specifies the number of bytes of options returned.
maxlen
has no meaning for the req
argument, but must be set in the ret argument
to specify the maximum number of bytes the options buffer
can hold.
The actual structure and content of the options is imposed by the
transport provider.
The flags
field of req
can specify one of the following actions:
flags
field of ret either has
T_SUCCESS or T_FAILURE
set to indicate to the user whether the options are supported.
These flags are only meaningful for the T_CHECK request.
opt
field of
ret.
In req, the len
field of opt
must be zero, and the buf
field may be NULL.
If issued as part of the connectionless-mode service, t_optmgmt may block due to flow control constraints. The function does not complete until the transport provider has processed all previously sent data units.
AT&T SVID Issue 3
;
X/Open CAE Specification, Networking Services, Issue 4, 1994.
;
and
Intel386 Binary Compatibility Specification, Edition 2 (iBCSe2)
.