HP-UX Reference (11i v1 05/09) - 3 Library Functions N-Z (vol 7)

t
t_optmgmt(3) t_optmgmt(3)
attempts to send the pending data within the linger period before closing the endpoint.
Data still pending after the linger period has elapsed is discarded.
Depending on the implementation,
t_close() or close() either block for at max-
imum the linger period, or immediately return, whereupon the system holds the connec-
tion in existence for at most the linger period.
The option constists of a structure
t_linger
declared as:
struct t_linger{
t_uscalar_t l_onoff; /* switch option on/off */
t_uscalar_t l_linger; /* linger period in seconds */
}
Legal values for the l_onoff are:
T_NO switch option off
T_YES activate option
The value of l_onoff is an absolute requirement.
The field l_linger determines the linger period in seconds. The transport user can
request the default value by setting the field to T_UNSPEC. The default timeout value
depends on the underlying transport provider (it is often T_INFINITE). Legal values for
this field are T_UNSPEC, T_INFINITE, and all non-negative numbers.
The l_linger value is not an absolute requirement. The implementation may place upper
and lower limits to this value. Requests that fall short of the lower limit are negotiated
to the lower limit.
Note that this option does not linger the execution of t_snddis() .
XTI_RCVBUF This option is used to adjust the internal buffer size allocated for the receive buffer. The
buffer size may be increased for high-volume connections, or decreased to limit the possi-
ble backlog of incoming data. Default and maximum buffer sizes are protocol-dependent;
see individual protocol manual entries, such as tcp(7P) and udp(7P). Maximum buffer
size is controlled by the ndd variables tcp_recv_hiwater_max and udp_recv_hiwater_max
depending upon the underlying protocol in use.
This request is not an absolute requirement. The implementation may place upper and
lower limits on the option value. Requests that fall short of the lower limit are nego-
tiated to the lower limit.
Legal values are all positive numbers.
XTI_RCVLOWAT
This option is used to set a low-water mark in the receive buffer. The option values gives
the minimal number of bytes that must have accumulated in the receive buffer before
they become visible to the transport user. If and when the amount of accumulated
receive data exceeds the low-water mark, a T_DATA event is created, an event mechan-
ism (e.g. poll() or select() ) indicates the data, and the data can be read by
t_rcv() or t_rcvudata() .
This request is not an absolute requirement. The implementation may place upper and
lower limits on the option value. Requests that fall short of the lower limit are nego-
tiated to the lower limit.
Legal values are all positive numbers.
XTI_SNDBUF This option is used to adjust the internal buffer size allocated for the send buffer. The
default maximum size of this buffer is controlled by the ndd variable
tcp_xmit_hiwater_max.
This request is not an absolute requirement. The implementation may place upper and
lower limits on the option value. Requests that fall short of the lower limit are nego-
tiated to the lower limit.
Legal values are all positive numbers.
XTI_SNDLOWAT This option is used to set a low-water mark in the send buffer. The option value gives
the minimal number of bytes that must have accumulated in the send buffer before they
are sent.
HP-UX 11i Version 1: September 2005 − 4 − Hewlett-Packard Company Section 3−−973