1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. Neither the name of the University nor the names of its contributors 13.\" may be used to endorse or promote products derived from this software 14.\" without specific prior written permission. 15.\" 16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 19.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 26.\" SUCH DAMAGE. 27.\" 28.\" @(#)getsockopt.2 8.4 (Berkeley) 5/2/95 29.\" $FreeBSD: src/lib/libc/sys/getsockopt.2,v 1.12.2.11 2002/01/09 17:44:15 yar Exp $ 30.\" 31.Dd August 7, 2019 32.Dt GETSOCKOPT 2 33.Os 34.Sh NAME 35.Nm getsockopt , 36.Nm setsockopt 37.Nd get and set options on sockets 38.Sh LIBRARY 39.Lb libc 40.Sh SYNOPSIS 41.In sys/types.h 42.In sys/socket.h 43.Ft int 44.Fn getsockopt "int s" "int level" "int optname" "void *optval" "socklen_t *optlen" 45.Ft int 46.Fn setsockopt "int s" "int level" "int optname" "const void *optval" "socklen_t optlen" 47.Sh DESCRIPTION 48.Fn Getsockopt 49and 50.Fn setsockopt 51manipulate the 52.Em options 53associated with a socket. Options may exist at multiple 54protocol levels; they are always present at the uppermost 55.Dq socket 56level. 57.Pp 58When manipulating socket options the level at which the 59option resides and the name of the option must be specified. 60To manipulate options at the socket level, 61.Fa level 62is specified as 63.Dv SOL_SOCKET . 64To manipulate options at any 65other level the protocol number of the appropriate protocol 66controlling the option is supplied. For example, 67to indicate that an option is to be interpreted by the 68.Tn TCP 69protocol, 70.Fa level 71should be set to the protocol number of 72.Tn TCP ; 73see 74.Xr getprotoent 3 . 75.Pp 76The parameters 77.Fa optval 78and 79.Fa optlen 80are used to access option values for 81.Fn setsockopt . 82For 83.Fn getsockopt 84they identify a buffer in which the value for the 85requested option(s) are to be returned. For 86.Fn getsockopt , 87.Fa optlen 88is a value-result parameter, initially containing the 89size of the buffer pointed to by 90.Fa optval , 91and modified on return to indicate the actual size of 92the value returned. If no option value is 93to be supplied or returned, 94.Fa optval 95may be NULL. 96.Pp 97.Fa Optname 98and any specified options are passed uninterpreted to the appropriate 99protocol module for interpretation. 100The include file 101.In sys/socket.h 102contains definitions for 103socket level options, described below. 104Options at other protocol levels vary in format and 105name; consult the appropriate entries in 106section 1074 of the manual. 108.Pp 109Most socket-level options utilize an 110.Fa int 111parameter for 112.Fa optval . 113For 114.Fn setsockopt , 115the parameter should be non-zero to enable a boolean option, 116or zero if the option is to be disabled. 117.Dv SO_LINGER 118uses a 119.Fa struct linger 120parameter, defined in 121.In sys/socket.h , 122which specifies the desired state of the option and the 123linger interval (see below). 124.Dv SO_SNDTIMEO 125and 126.Dv SO_RCVTIMEO 127use a 128.Fa struct timeval 129parameter, defined in 130.In sys/time.h . 131.Pp 132The following options are recognized at the socket level. 133Except as noted, each may be examined with 134.Fn getsockopt 135and set with 136.Fn setsockopt . 137.Bl -column SO_ACCEPTFILTER -offset indent 138.It Dv SO_DEBUG Ta "enables recording of debugging information" 139.It Dv SO_REUSEADDR Ta "enables local address reuse" 140.It Dv SO_REUSEPORT Ta "enables duplicate address and port bindings" 141.It Dv SO_KEEPALIVE Ta "enables keep connections alive" 142.It Dv SO_DONTROUTE Ta "enables routing bypass for outgoing messages" 143.It Dv SO_LINGER Ta "linger on close if data present" 144.It Dv SO_BROADCAST Ta "enables permission to transmit broadcast messages" 145.It Dv SO_OOBINLINE Ta "enables reception of out-of-band data in band" 146.It Dv SO_SNDBUF Ta "set buffer size for output" 147.It Dv SO_RCVBUF Ta "set buffer size for input" 148.It Dv SO_SNDLOWAT Ta "set minimum count for output" 149.It Dv SO_RCVLOWAT Ta "set minimum count for input" 150.It Dv SO_SNDTIMEO Ta "set timeout value for output" 151.It Dv SO_RCVTIMEO Ta "set timeout value for input" 152.It Dv SO_ACCEPTFILTER Ta "set accept filter on listening socket" 153.It Dv SO_TYPE Ta "get the type of the socket (get only)" 154.It Dv SO_ERROR Ta "get and clear error on the socket (get only)" 155.It Dv SO_RERROR Ta "enables receive error reporting" 156.El 157.Pp 158.Dv SO_DEBUG 159enables debugging in the underlying protocol modules. 160.Dv SO_REUSEADDR 161indicates that the rules used in validating addresses supplied 162in a 163.Xr bind 2 164call should allow reuse of local addresses. 165.Dv SO_REUSEPORT 166allows completely duplicate bindings by multiple processes 167if they all set 168.Dv SO_REUSEPORT 169before binding the port. 170This option permits multiple instances of a program to each 171receive UDP/IP multicast or broadcast datagrams destined for the bound port. 172.Dv SO_KEEPALIVE 173enables the 174periodic transmission of messages on a connected socket. Should the 175connected party fail to respond to these messages, the connection is 176considered broken and processes using the socket are notified via a 177.Dv SIGPIPE 178signal when attempting to send data. 179.Dv SO_DONTROUTE 180indicates that outgoing messages should 181bypass the standard routing facilities. Instead, messages are directed 182to the appropriate network interface according to the network portion 183of the destination address. 184.Dv SO_RERROR 185indicates that receive buffer overflows should be handled as errors. 186Historically receive buffer overflows have been ignored and programs 187could not tell if they missed messages or messages had been truncated 188because of overflows. 189Since programs historically do not expect to get receive overflow errors, 190this behavior is not the default. 191.Pp 192.Dv SO_LINGER 193controls the action taken when unsent messages 194are queued on socket and a 195.Xr close 2 196is performed. 197If the socket promises reliable delivery of data and 198.Dv SO_LINGER 199is set, 200the system will block the process on the 201.Xr close 2 202attempt until it is able to transmit the data or until it decides it 203is unable to deliver the information (a timeout period, termed the 204linger interval, is specified in seconds in the 205.Fn setsockopt 206call when 207.Dv SO_LINGER 208is requested). 209If 210.Dv SO_LINGER 211is disabled and a 212.Xr close 2 213is issued, the system will process the close in a manner that allows 214the process to continue as quickly as possible. 215.Pp 216The option 217.Dv SO_BROADCAST 218requests permission to send broadcast datagrams 219on the socket. 220Broadcast was a privileged operation in earlier versions of the system. 221With protocols that support out-of-band data, the 222.Dv SO_OOBINLINE 223option 224requests that out-of-band data be placed in the normal data input queue 225as received; it will then be accessible with 226.Xr recv 2 227or 228.Xr read 2 229calls without the 230.Dv MSG_OOB 231flag. 232Some protocols always behave as if this option is set. 233.Dv SO_SNDBUF 234and 235.Dv SO_RCVBUF 236are options to adjust the normal 237buffer sizes allocated for output and input buffers, respectively. 238The buffer size may be increased for high-volume connections, 239or may be decreased to limit the possible backlog of incoming data. 240The system places an absolute maximum on these values, which is accessible 241through the 242.Xr sysctl 3 243MIB variable 244.Va kern.ipc.maxsockbuf . 245.Pp 246.Dv SO_SNDLOWAT 247is an option to set the minimum count for output operations. 248Most output operations process all of the data supplied 249by the call, delivering data to the protocol for transmission 250and blocking as necessary for flow control. 251Nonblocking output operations will process as much data as permitted 252subject to flow control without blocking, but will process no data 253if flow control does not allow the smaller of the low water mark value 254or the entire request to be processed. 255A 256.Xr select 2 257operation testing the ability to write to a socket will return true 258only if the low water mark amount could be processed. 259The default value for 260.Dv SO_SNDLOWAT 261is set to a convenient size for network efficiency, often 1024. 262.Dv SO_RCVLOWAT 263is an option to set the minimum count for input operations. 264In general, receive calls will block until any (non-zero) amount of data 265is received, then return with the smaller of the amount available or the amount 266requested. 267The default value for 268.Dv SO_RCVLOWAT 269is 1. 270If 271.Dv SO_RCVLOWAT 272is set to a larger value, blocking receive calls normally 273wait until they have received the smaller of the low water mark value 274or the requested amount. 275Receive calls may still return less than the low water mark if an error 276occurs, a signal is caught, or the type of data next in the receive queue 277is different from that which was returned. 278.Pp 279.Dv SO_SNDTIMEO 280is an option to set a timeout value for output operations. 281It accepts a 282.Fa struct timeval 283parameter with the number of seconds and microseconds 284used to limit waits for output operations to complete. 285If a send operation has blocked for this much time, 286it returns with a partial count 287or with the error 288.Er EWOULDBLOCK 289if no data were sent. 290In the current implementation, this timer is restarted each time additional 291data are delivered to the protocol, 292implying that the limit applies to output portions ranging in size 293from the low water mark to the high water mark for output. 294.Dv SO_RCVTIMEO 295is an option to set a timeout value for input operations. 296It accepts a 297.Fa struct timeval 298parameter with the number of seconds and microseconds 299used to limit waits for input operations to complete. 300In the current implementation, this timer is restarted each time additional 301data are received by the protocol, 302and thus the limit is in effect an inactivity timer. 303If a receive operation has been blocked for this much time without 304receiving additional data, it returns with a short count 305or with the error 306.Er EWOULDBLOCK 307if no data were received. 308.Pp 309.Dv SO_ACCEPTFILTER 310places an 311.Xr accept_filter 9 312on the socket, 313which will filter incoming connections 314on a listening stream socket before being presented for 315.Xr accept 2 . 316Once more, 317.Xr listen 2 318must be called on the socket before 319trying to install the filter on it, 320or else the 321.Fn setsockopt 322call will fail. 323.Bd -literal 324struct accept_filter_arg { 325 char af_name[16]; 326 char af_arg[256-16]; 327}; 328.Ed 329.Pp 330.Fa optval 331should point to a 332.Fa struct accept_filter_arg 333that will select and configure the 334.Xr accept_filter 9 . 335.Fa af_name 336should be filled with the name of the accept filter 337that the application wishes to place on the listening socket. 338.Fa af_arg 339is an optional parameter that can be passed to the accept 340filter specified by 341.Fa af_name 342to provide additional configuration options at attach time. 343Passing in an 344.Fa optval 345of NULL will remove the filter. 346.Pp 347Finally, 348.Dv SO_TYPE 349and 350.Dv SO_ERROR 351are options used only with 352.Fn getsockopt . 353.Dv SO_TYPE 354returns the type of the socket, such as 355.Dv SOCK_STREAM ; 356it is useful for servers that inherit sockets on startup. 357.Dv SO_ERROR 358returns any pending error on the socket and clears 359the error status. 360It may be used to check for asynchronous errors on connected 361datagram sockets or for other asynchronous errors. 362.Sh RETURN VALUES 363.Rv -std 364.Sh ERRORS 365The call succeeds unless: 366.Bl -tag -width Er 367.It Bq Er EBADF 368The argument 369.Fa s 370is not a valid descriptor. 371.It Bq Er ENOTSOCK 372The argument 373.Fa s 374is a file, not a socket. 375.It Bq Er ENOPROTOOPT 376The option is unknown at the level indicated. 377.It Bq Er EFAULT 378The address pointed to by 379.Fa optval 380is not in a valid part of the process address space. 381For 382.Fn getsockopt , 383this error may also be returned if 384.Fa optlen 385is not in a valid part of the process address space. 386.It Bq Er EINVAL 387Installing an 388.Xr accept_filter 9 389on a non-listening socket was attempted. 390.El 391.Sh SEE ALSO 392.Xr ioctl 2 , 393.Xr socket 2 , 394.Xr getprotoent 3 , 395.Xr sysctl 3 , 396.Xr protocols 5 , 397.Xr sysctl 8 , 398.Xr accept_filter 9 399.Sh HISTORY 400The 401.Fn getsockopt 402system call appeared in 403.Bx 4.2 . 404.Sh BUGS 405Several of the socket options should be handled at lower levels of the system. 406