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.\" 4. 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$ 30.\" 31.Dd March 8, 2007 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 * restrict optval" "socklen_t * restrict optlen" 45.Ft int 46.Fn setsockopt "int s" "int level" "int optname" "const void *optval" "socklen_t optlen" 47.Sh DESCRIPTION 48The 49.Fn getsockopt 50and 51.Fn setsockopt 52system calls 53manipulate the 54.Em options 55associated with a socket. 56Options may exist at multiple 57protocol levels; they are always present at the uppermost 58.Dq socket 59level. 60.Pp 61When manipulating socket options the level at which the 62option resides and the name of the option must be specified. 63To manipulate options at the socket level, 64.Fa level 65is specified as 66.Dv SOL_SOCKET . 67To manipulate options at any 68other level the protocol number of the appropriate protocol 69controlling the option is supplied. 70For example, 71to indicate that an option is to be interpreted by the 72.Tn TCP 73protocol, 74.Fa level 75should be set to the protocol number of 76.Tn TCP ; 77see 78.Xr getprotoent 3 . 79.Pp 80The 81.Fa optval 82and 83.Fa optlen 84arguments 85are used to access option values for 86.Fn setsockopt . 87For 88.Fn getsockopt 89they identify a buffer in which the value for the 90requested option(s) are to be returned. 91For 92.Fn getsockopt , 93.Fa optlen 94is a value-result argument, initially containing the 95size of the buffer pointed to by 96.Fa optval , 97and modified on return to indicate the actual size of 98the value returned. 99If no option value is 100to be supplied or returned, 101.Fa optval 102may be NULL. 103.Pp 104The 105.Fa optname 106argument 107and any specified options are passed uninterpreted to the appropriate 108protocol module for interpretation. 109The include file 110.In sys/socket.h 111contains definitions for 112socket level options, described below. 113Options at other protocol levels vary in format and 114name; consult the appropriate entries in 115section 1164 of the manual. 117.Pp 118Most socket-level options utilize an 119.Vt int 120argument for 121.Fa optval . 122For 123.Fn setsockopt , 124the argument should be non-zero to enable a boolean option, 125or zero if the option is to be disabled. 126.Dv SO_LINGER 127uses a 128.Vt "struct linger" 129argument, defined in 130.In sys/socket.h , 131which specifies the desired state of the option and the 132linger interval (see below). 133.Dv SO_SNDTIMEO 134and 135.Dv SO_RCVTIMEO 136use a 137.Vt "struct timeval" 138argument, defined in 139.In sys/time.h . 140.Pp 141The following options are recognized at the socket level. 142Except as noted, each may be examined with 143.Fn getsockopt 144and set with 145.Fn setsockopt . 146.Bl -column SO_ACCEPTFILTER -offset indent 147.It Dv SO_DEBUG Ta "enables recording of debugging information" 148.It Dv SO_REUSEADDR Ta "enables local address reuse" 149.It Dv SO_REUSEPORT Ta "enables duplicate address and port bindings" 150.It Dv SO_KEEPALIVE Ta "enables keep connections alive" 151.It Dv SO_DONTROUTE Ta "enables routing bypass for outgoing messages" 152.It Dv SO_LINGER Ta "linger on close if data present" 153.It Dv SO_BROADCAST Ta "enables permission to transmit broadcast messages" 154.It Dv SO_OOBINLINE Ta "enables reception of out-of-band data in band" 155.It Dv SO_SNDBUF Ta "set buffer size for output" 156.It Dv SO_RCVBUF Ta "set buffer size for input" 157.It Dv SO_SNDLOWAT Ta "set minimum count for output" 158.It Dv SO_RCVLOWAT Ta "set minimum count for input" 159.It Dv SO_SNDTIMEO Ta "set timeout value for output" 160.It Dv SO_RCVTIMEO Ta "set timeout value for input" 161.It Dv SO_ACCEPTFILTER Ta "set accept filter on listening socket" 162.It Dv SO_NOSIGPIPE Ta 163controls generation of 164.Dv SIGPIPE 165for the socket 166.It Dv SO_TIMESTAMP Ta "enables reception of a timestamp with datagrams" 167.It Dv SO_BINTIME Ta "enables reception of a timestamp with datagrams" 168.It Dv SO_ACCEPTCONN Ta "get listening status of the socket (get only)" 169.It Dv SO_TYPE Ta "get the type of the socket (get only)" 170.It Dv SO_ERROR Ta "get and clear error on the socket (get only)" 171.It Dv SO_SETFIB Ta "set the associated FIB (routing table) for the socket (set only)" 172.El 173.Pp 174.Dv SO_DEBUG 175enables debugging in the underlying protocol modules. 176.Dv SO_REUSEADDR 177indicates that the rules used in validating addresses supplied 178in a 179.Xr bind 2 180system call should allow reuse of local addresses. 181.Dv SO_REUSEPORT 182allows completely duplicate bindings by multiple processes 183if they all set 184.Dv SO_REUSEPORT 185before binding the port. 186This option permits multiple instances of a program to each 187receive UDP/IP multicast or broadcast datagrams destined for the bound port. 188.Dv SO_KEEPALIVE 189enables the 190periodic transmission of messages on a connected socket. 191Should the 192connected party fail to respond to these messages, the connection is 193considered broken and processes using the socket are notified via a 194.Dv SIGPIPE 195signal when attempting to send data. 196.Dv SO_DONTROUTE 197indicates that outgoing messages should 198bypass the standard routing facilities. 199Instead, messages are directed 200to the appropriate network interface according to the network portion 201of the destination address. 202.Pp 203.Dv SO_LINGER 204controls the action taken when unsent messages 205are queued on socket and a 206.Xr close 2 207is performed. 208If the socket promises reliable delivery of data and 209.Dv SO_LINGER 210is set, 211the system will block the process on the 212.Xr close 2 213attempt until it is able to transmit the data or until it decides it 214is unable to deliver the information (a timeout period, termed the 215linger interval, is specified in seconds in the 216.Fn setsockopt 217system call when 218.Dv SO_LINGER 219is requested). 220If 221.Dv SO_LINGER 222is disabled and a 223.Xr close 2 224is issued, the system will process the close in a manner that allows 225the process to continue as quickly as possible. 226.Pp 227The option 228.Dv SO_BROADCAST 229requests permission to send broadcast datagrams 230on the socket. 231Broadcast was a privileged operation in earlier versions of the system. 232With protocols that support out-of-band data, the 233.Dv SO_OOBINLINE 234option 235requests that out-of-band data be placed in the normal data input queue 236as received; it will then be accessible with 237.Xr recv 2 238or 239.Xr read 2 240calls without the 241.Dv MSG_OOB 242flag. 243Some protocols always behave as if this option is set. 244.Dv SO_SNDBUF 245and 246.Dv SO_RCVBUF 247are options to adjust the normal 248buffer sizes allocated for output and input buffers, respectively. 249The buffer size may be increased for high-volume connections, 250or may be decreased to limit the possible backlog of incoming data. 251The system places an absolute maximum on these values, which is accessible 252through the 253.Xr sysctl 3 254MIB variable 255.Dq Li kern.ipc.maxsockbuf . 256.Pp 257.Dv SO_SNDLOWAT 258is an option to set the minimum count for output operations. 259Most output operations process all of the data supplied 260by the call, delivering data to the protocol for transmission 261and blocking as necessary for flow control. 262Nonblocking output operations will process as much data as permitted 263subject to flow control without blocking, but will process no data 264if flow control does not allow the smaller of the low water mark value 265or the entire request to be processed. 266A 267.Xr select 2 268operation testing the ability to write to a socket will return true 269only if the low water mark amount could be processed. 270The default value for 271.Dv SO_SNDLOWAT 272is set to a convenient size for network efficiency, often 1024. 273.Dv SO_RCVLOWAT 274is an option to set the minimum count for input operations. 275In general, receive calls will block until any (non-zero) amount of data 276is received, then return with the smaller of the amount available or the amount 277requested. 278The default value for 279.Dv SO_RCVLOWAT 280is 1. 281If 282.Dv SO_RCVLOWAT 283is set to a larger value, blocking receive calls normally 284wait until they have received the smaller of the low water mark value 285or the requested amount. 286Receive calls may still return less than the low water mark if an error 287occurs, a signal is caught, or the type of data next in the receive queue 288is different from that which was returned. 289.Pp 290.Dv SO_SNDTIMEO 291is an option to set a timeout value for output operations. 292It accepts a 293.Vt "struct timeval" 294argument with the number of seconds and microseconds 295used to limit waits for output operations to complete. 296If a send operation has blocked for this much time, 297it returns with a partial count 298or with the error 299.Er EWOULDBLOCK 300if no data were sent. 301In the current implementation, this timer is restarted each time additional 302data are delivered to the protocol, 303implying that the limit applies to output portions ranging in size 304from the low water mark to the high water mark for output. 305.Dv SO_RCVTIMEO 306is an option to set a timeout value for input operations. 307It accepts a 308.Vt "struct timeval" 309argument with the number of seconds and microseconds 310used to limit waits for input operations to complete. 311In the current implementation, this timer is restarted each time additional 312data are received by the protocol, 313and thus the limit is in effect an inactivity timer. 314If a receive operation has been blocked for this much time without 315receiving additional data, it returns with a short count 316or with the error 317.Er EWOULDBLOCK 318if no data were received. 319.Pp 320.Dv SO_SETFIB 321can be used to over-ride the default FIB (routing table) for the given socket. 322The value must be from 0 to one less than the number returned from 323the sysctl 324.Em net.fibs . 325.Pp 326.Dv SO_ACCEPTFILTER 327places an 328.Xr accept_filter 9 329on the socket, 330which will filter incoming connections 331on a listening stream socket before being presented for 332.Xr accept 2 . 333Once more, 334.Xr listen 2 335must be called on the socket before 336trying to install the filter on it, 337or else the 338.Fn setsockopt 339system call will fail. 340.Bd -literal 341struct accept_filter_arg { 342 char af_name[16]; 343 char af_arg[256-16]; 344}; 345.Ed 346.Pp 347The 348.Fa optval 349argument 350should point to a 351.Fa struct accept_filter_arg 352that will select and configure the 353.Xr accept_filter 9 . 354The 355.Fa af_name 356argument 357should be filled with the name of the accept filter 358that the application wishes to place on the listening socket. 359The optional argument 360.Fa af_arg 361can be passed to the accept 362filter specified by 363.Fa af_name 364to provide additional configuration options at attach time. 365Passing in an 366.Fa optval 367of NULL will remove the filter. 368.Pp 369The 370.Dv SO_NOSIGPIPE 371option controls generation of the 372.Dv SIGPIPE 373signal normally sent 374when writing to a connected socket where the other end has been 375closed returns with the error 376.Er EPIPE . 377.Pp 378If the 379.Dv SO_TIMESTAMP 380or 381.Dv SO_BINTIME 382option is enabled on a 383.Dv SOCK_DGRAM 384socket, the 385.Xr recvmsg 2 386call will return a timestamp corresponding to when the datagram was received. 387The 388.Va msg_control 389field in the 390.Vt msghdr 391structure points to a buffer that contains a 392.Vt cmsghdr 393structure followed by a 394.Vt "struct timeval" 395for 396.Dv SO_TIMESTAMP 397and 398.Vt "struct bintime" 399for 400.Dv SO_BINTIME . 401The 402.Vt cmsghdr 403fields have the following values for TIMESTAMP: 404.Bd -literal 405 cmsg_len = sizeof(struct timeval); 406 cmsg_level = SOL_SOCKET; 407 cmsg_type = SCM_TIMESTAMP; 408.Ed 409.Pp 410and for 411.Dv SO_BINTIME : 412.Bd -literal 413 cmsg_len = sizeof(struct bintime); 414 cmsg_level = SOL_SOCKET; 415 cmsg_type = SCM_BINTIME; 416.Ed 417.Pp 418Finally, 419.Dv SO_ACCEPTCONN , 420.Dv SO_TYPE 421and 422.Dv SO_ERROR 423are options used only with 424.Fn getsockopt . 425.Dv SO_ACCEPTCONN 426returns whether the socket is currently accepting connections, 427that is, whether or not the 428.Xr listen 2 429system call was invoked on the socket. 430.Dv SO_TYPE 431returns the type of the socket, such as 432.Dv SOCK_STREAM ; 433it is useful for servers that inherit sockets on startup. 434.Dv SO_ERROR 435returns any pending error on the socket and clears 436the error status. 437It may be used to check for asynchronous errors on connected 438datagram sockets or for other asynchronous errors. 439.Sh RETURN VALUES 440.Rv -std 441.Sh ERRORS 442The call succeeds unless: 443.Bl -tag -width Er 444.It Bq Er EBADF 445The argument 446.Fa s 447is not a valid descriptor. 448.It Bq Er ENOTSOCK 449The argument 450.Fa s 451is a file, not a socket. 452.It Bq Er ENOPROTOOPT 453The option is unknown at the level indicated. 454.It Bq Er EFAULT 455The address pointed to by 456.Fa optval 457is not in a valid part of the process address space. 458For 459.Fn getsockopt , 460this error may also be returned if 461.Fa optlen 462is not in a valid part of the process address space. 463.It Bq Er EINVAL 464Installing an 465.Xr accept_filter 9 466on a non-listening socket was attempted. 467.El 468.Sh SEE ALSO 469.Xr ioctl 2 , 470.Xr listen 2 , 471.Xr recvmsg 2 , 472.Xr socket 2 , 473.Xr getprotoent 3 , 474.Xr sysctl 3 , 475.Xr protocols 5 , 476.Xr sysctl 8 , 477.Xr accept_filter 9 , 478.Xr bintime 9 479.Sh HISTORY 480The 481.Fn getsockopt 482system call appeared in 483.Bx 4.2 . 484.Sh BUGS 485Several of the socket options should be handled at lower levels of the system. 486