main()
{
创建socket 并listen；
signal( SIGCHLD, SIG_IGN );
for(i=1; i<= 5; i++) //循环fork5个子进程
{
j := fork(); //
if j=0
{
while (1)
{
accept();
if accept 成功
处理对应的信息请求;
else
exit
}
}
}
}
该进程为多线程，目的是处理多个客户端的连接请求。但启动后，没有客户端或者有客户端连接时，accept都偶尔报错：Resource temporarily unavailable。
以前在sco下编译和运行都问题的，但移植到 AIX（64位）编译和运行就报错了。查了很久，不知道何解。。
17 个解决方案
#1
you must use setsockopt function to control the socket's operation:
SO_REUSEADDR
SO_KEEPALIVE
SO_LINGER
SO_RCVTIMEO
SO_SNDTIMEO
SO_REUSEADDR
SO_KEEPALIVE
SO_LINGER
SO_RCVTIMEO
SO_SNDTIMEO
#2
帮顶~
#3
请问datacodebugs ；在哪设置?因为本人初次接触 socket编程，不太熟悉
#4
NAME
getsockopt, setsockopt -- get and set options on sockets
SYNOPSIS
#include <sys/socket.h>
int
getsockopt(int socket, int level, int option_name,
void *restrict option_value, socklen_t *restrict option_len);
int
setsockopt(int socket, int level, int option_name,
const void *option_value, socklen_t option_len);
DESCRIPTION
Getsockopt() and setsockopt() manipulate the options associated with a
socket. Options may exist at multiple protocol levels; they are always
present at the uppermost ``socket'' level.
When manipulating socket options the level at which the option resides
and the name of the option must be specified. To manipulate options at
the socket level, level is specified as SOL_SOCKET. To manipulate
options at any other level the protocol number of the appropriate proto-
col controlling the option is supplied. For example, to indicate that an
option is to be interpreted by the TCP protocol, level should be set to
the protocol number of TCP; see getprotoent(3).
The parameters option_value and option_len are used to access option val-
ues for setsockopt(). For getsockopt() they identify a buffer in which
the value for the requested option(s) are to be returned. For
getsockopt(), option_len is a value-result parameter, initially contain-
ing the size of the buffer pointed to by option_value, and modified on
return to indicate the actual size of the value returned. If no option
value is to be supplied or returned, option_value may be NULL.
option_name and any specified options are passed uninterpreted to the
appropriate protocol module for interpretation. The include file
<sys/socket.h> contains definitions for socket level options, described
below. Options at other protocol levels vary in format and name; consult
the appropriate entries in section 4 of the manual.
Most socket-level options utilize an int parameter for option_value. For
setsockopt(), the parameter should be non-zero to enable a boolean
option, or zero if the option is to be disabled. SO_LINGER uses a struct
linger parameter, defined in <sys/socket.h>, which specifies the desired
state of the option and the linger interval (see below). SO_SNDTIMEO and
SO_RCVTIMEO use a struct timeval parameter, defined in <sys/time.h>.
The following options are recognized at the socket level. Except as
noted, each may be examined with getsockopt() and set with setsockopt().
SO_DEBUG enables recording of debugging information
SO_REUSEADDR enables local address reuse
SO_REUSEPORT enables duplicate address and port bindings
SO_KEEPALIVE enables keep connections alive
SO_DONTROUTE enables routing bypass for outgoing messages
SO_LINGER linger on close if data present
SO_BROADCAST enables permission to transmit broadcast messages
SO_OOBINLINE enables reception of out-of-band data in band
SO_SNDBUF set buffer size for output
SO_RCVBUF set buffer size for input
SO_SNDLOWAT set minimum count for output
SO_RCVLOWAT set minimum count for input
SO_SNDTIMEO set timeout value for output
SO_RCVTIMEO set timeout value for input
SO_TYPE get the type of the socket (get only)
SO_ERROR get and clear error on the socket (get only)
SO_NOSIGPIPE do not generate SIGPIPE, instead return EPIPE
SO_DEBUG enables debugging in the underlying protocol modules.
SO_REUSEADDR indicates that the rules used in validating addresses sup-
plied in a bind(2) call should allow reuse of local addresses.
SO_REUSEPORT allows completely duplicate bindings by multiple processes
if they all set SO_REUSEPORT before binding the port. This option per-
mits multiple instances of a program to each receive UDP/IP multicast or
broadcast datagrams destined for the bound port. SO_KEEPALIVE enables
the periodic transmission of messages on a connected socket. Should the
connected party fail to respond to these messages, the connection is con-
sidered broken and processes using the socket are notified via a SIGPIPE
signal when attempting to send data. SO_DONTROUTE indicates that outgo-
ing messages should bypass the standard routing facilities. Instead,
messages are directed to the appropriate network interface according to
the network portion of the destination address.
getsockopt, setsockopt -- get and set options on sockets
SYNOPSIS
#include <sys/socket.h>
int
getsockopt(int socket, int level, int option_name,
void *restrict option_value, socklen_t *restrict option_len);
int
setsockopt(int socket, int level, int option_name,
const void *option_value, socklen_t option_len);
DESCRIPTION
Getsockopt() and setsockopt() manipulate the options associated with a
socket. Options may exist at multiple protocol levels; they are always
present at the uppermost ``socket'' level.
When manipulating socket options the level at which the option resides
and the name of the option must be specified. To manipulate options at
the socket level, level is specified as SOL_SOCKET. To manipulate
options at any other level the protocol number of the appropriate proto-
col controlling the option is supplied. For example, to indicate that an
option is to be interpreted by the TCP protocol, level should be set to
the protocol number of TCP; see getprotoent(3).
The parameters option_value and option_len are used to access option val-
ues for setsockopt(). For getsockopt() they identify a buffer in which
the value for the requested option(s) are to be returned. For
getsockopt(), option_len is a value-result parameter, initially contain-
ing the size of the buffer pointed to by option_value, and modified on
return to indicate the actual size of the value returned. If no option
value is to be supplied or returned, option_value may be NULL.
option_name and any specified options are passed uninterpreted to the
appropriate protocol module for interpretation. The include file
<sys/socket.h> contains definitions for socket level options, described
below. Options at other protocol levels vary in format and name; consult
the appropriate entries in section 4 of the manual.
Most socket-level options utilize an int parameter for option_value. For
setsockopt(), the parameter should be non-zero to enable a boolean
option, or zero if the option is to be disabled. SO_LINGER uses a struct
linger parameter, defined in <sys/socket.h>, which specifies the desired
state of the option and the linger interval (see below). SO_SNDTIMEO and
SO_RCVTIMEO use a struct timeval parameter, defined in <sys/time.h>.
The following options are recognized at the socket level. Except as
noted, each may be examined with getsockopt() and set with setsockopt().
SO_DEBUG enables recording of debugging information
SO_REUSEADDR enables local address reuse
SO_REUSEPORT enables duplicate address and port bindings
SO_KEEPALIVE enables keep connections alive
SO_DONTROUTE enables routing bypass for outgoing messages
SO_LINGER linger on close if data present
SO_BROADCAST enables permission to transmit broadcast messages
SO_OOBINLINE enables reception of out-of-band data in band
SO_SNDBUF set buffer size for output
SO_RCVBUF set buffer size for input
SO_SNDLOWAT set minimum count for output
SO_RCVLOWAT set minimum count for input
SO_SNDTIMEO set timeout value for output
SO_RCVTIMEO set timeout value for input
SO_TYPE get the type of the socket (get only)
SO_ERROR get and clear error on the socket (get only)
SO_NOSIGPIPE do not generate SIGPIPE, instead return EPIPE
SO_DEBUG enables debugging in the underlying protocol modules.
SO_REUSEADDR indicates that the rules used in validating addresses sup-
plied in a bind(2) call should allow reuse of local addresses.
SO_REUSEPORT allows completely duplicate bindings by multiple processes
if they all set SO_REUSEPORT before binding the port. This option per-
mits multiple instances of a program to each receive UDP/IP multicast or
broadcast datagrams destined for the bound port. SO_KEEPALIVE enables
the periodic transmission of messages on a connected socket. Should the
connected party fail to respond to these messages, the connection is con-
sidered broken and processes using the socket are notified via a SIGPIPE
signal when attempting to send data. SO_DONTROUTE indicates that outgo-
ing messages should bypass the standard routing facilities. Instead,
messages are directed to the appropriate network interface according to
the network portion of the destination address.
#5
SO_LINGER controls the action taken when unsent messages are queued on
socket and a close(2) is performed. If the socket promises reliable
delivery of data and SO_LINGER is set, the system will block the process
on the close attempt until it is able to transmit the data or until it
decides it is unable to deliver the information (a timeout period, termed
the linger interval, is specified in the setsockopt() call when SO_LINGER
is requested). If SO_LINGER is disabled and a close is issued, the sys-
tem will process the close in a manner that allows the process to con-
tinue as quickly as possible.
The option SO_BROADCAST requests permission to send broadcast datagrams
on the socket. Broadcast was a privileged operation in earlier versions
of the system. With protocols that support out-of-band data, the
SO_OOBINLINE option requests that out-of-band data be placed in the nor-
mal data input queue as received; it will then be accessible with recv or
read calls without the MSG_OOB flag. Some protocols always behave as if
this option is set. SO_SNDBUF and SO_RCVBUF are options to adjust the
normal buffer sizes allocated for output and input buffers, respectively.
The buffer size may be increased for high-volume connections, or may be
decreased to limit the possible backlog of incoming data. The system
places an absolute limit on these values.
SO_SNDLOWAT is an option to set the minimum count for output operations.
Most output operations process all of the data supplied by the call,
delivering data to the protocol for transmission and blocking as neces-
sary for flow control. Nonblocking output operations will process as
much data as permitted (subject to flow control) without blocking, but
will process no data if flow control does not allow the smaller of the
low-water mark value or the entire request to be processed. A select(2)
operation testing the ability to write to a socket will return true only
if the low-water mark amount could be processed. The default value for
SO_SNDLOWAT is set to a convenient size for network efficiency, often
1024.
SO_RCVLOWAT is an option to set the minimum count for input operations.
In general, receive calls will block until any (non-zero) amount of data
is received, then return with the smaller of the amount available or the
amount requested. The default value for SO_RCVLOWAT is 1. If
SO_RCVLOWAT is set to a larger value, blocking receive calls normally
wait until they have received the smaller of the low-water mark value or
the requested amount. Receive calls may still return less than the low-
water mark if an error occurs, a signal is caught, or the type of data
next in the receive queue is different than that returned.
SO_SNDTIMEO is an option to set a timeout value for output operations.
It accepts a struct timeval parameter with the number of seconds and
microseconds used to limit waits for output operations to complete. If a
send operation has blocked for this much time, it returns with a partial
count or with the error EWOULDBLOCK if no data were sent. In the current
implementation, this timer is restarted each time additional data are
delivered to the protocol, implying that the limit applies to output por-
tions ranging in size from the low-water mark to the high-water mark for
output.
SO_RCVTIMEO is an option to set a timeout value for input operations. It
accepts a struct timeval parameter with the number of seconds and
microseconds used to limit waits for input operations to complete. In
the current implementation, this timer is restarted each time additional
data are received by the protocol, and thus the limit is in effect an
inactivity timer. If a receive operation has been blocked for this much
time without receiving additional data, it returns with a short count or
with the error EWOULDBLOCK if no data were received. The struct timeval
parameter must represent a positive time interval; otherwise,
setsockopt() returns with the error EDOM.
SO_NOSIGPIPE is an option that prevents SIGPIPE from being raised when a
write fails on a socket to which there is no reader; instead, the write
to the socket returns with the error EPIPE when there is no reader.
Finally, SO_TYPE and SO_ERROR are options used only with getsockopt().
SO_TYPE returns the type of the socket, such as SOCK_STREAM; it is useful
for servers that inherit sockets on startup. SO_ERROR returns any pend-
ing error on the socket and clears the error status. It may be used to
check for asynchronous errors on connected datagram sockets or for other
asynchronous errors.
RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the
value -1 is returned and the global variable errno is set to indicate the
error.
ERRORS
The getsockopt() and setsockopt() system calls will succeed unless:
[EBADF] The argument socket is not a valid file descriptor.
[EFAULT] The address pointed to by option_value is not in a
valid part of the process address space. For
getsockopt(), this error may also be returned if
option_len is not in a valid part of the process
address space.
[EINVAL] The option is invalid at the level indicated.
[ENOBUFS] Insufficient memory buffers are available.
[ENOPROTOOPT] The option is unknown at the level indicated.
[ENOTSOCK] The argument socket is not a socket (e.g., a plain
file).
The setsockopt() system call will succeed unless:
[EDOM] The argument option_value is out of bounds.
[EISCONN] socket is already connected and a specified option
cannot be set while this is the case.
LEGACY SYNOPSIS
#include <sys/types.h>
#include <sys/socket.h>
The include file <sys/types.h> is necessary.
SEE ALSO
ioctl(2), socket(2), getprotoent(3), protocols(5)
socket and a close(2) is performed. If the socket promises reliable
delivery of data and SO_LINGER is set, the system will block the process
on the close attempt until it is able to transmit the data or until it
decides it is unable to deliver the information (a timeout period, termed
the linger interval, is specified in the setsockopt() call when SO_LINGER
is requested). If SO_LINGER is disabled and a close is issued, the sys-
tem will process the close in a manner that allows the process to con-
tinue as quickly as possible.
The option SO_BROADCAST requests permission to send broadcast datagrams
on the socket. Broadcast was a privileged operation in earlier versions
of the system. With protocols that support out-of-band data, the
SO_OOBINLINE option requests that out-of-band data be placed in the nor-
mal data input queue as received; it will then be accessible with recv or
read calls without the MSG_OOB flag. Some protocols always behave as if
this option is set. SO_SNDBUF and SO_RCVBUF are options to adjust the
normal buffer sizes allocated for output and input buffers, respectively.
The buffer size may be increased for high-volume connections, or may be
decreased to limit the possible backlog of incoming data. The system
places an absolute limit on these values.
SO_SNDLOWAT is an option to set the minimum count for output operations.
Most output operations process all of the data supplied by the call,
delivering data to the protocol for transmission and blocking as neces-
sary for flow control. Nonblocking output operations will process as
much data as permitted (subject to flow control) without blocking, but
will process no data if flow control does not allow the smaller of the
low-water mark value or the entire request to be processed. A select(2)
operation testing the ability to write to a socket will return true only
if the low-water mark amount could be processed. The default value for
SO_SNDLOWAT is set to a convenient size for network efficiency, often
1024.
SO_RCVLOWAT is an option to set the minimum count for input operations.
In general, receive calls will block until any (non-zero) amount of data
is received, then return with the smaller of the amount available or the
amount requested. The default value for SO_RCVLOWAT is 1. If
SO_RCVLOWAT is set to a larger value, blocking receive calls normally
wait until they have received the smaller of the low-water mark value or
the requested amount. Receive calls may still return less than the low-
water mark if an error occurs, a signal is caught, or the type of data
next in the receive queue is different than that returned.
SO_SNDTIMEO is an option to set a timeout value for output operations.
It accepts a struct timeval parameter with the number of seconds and
microseconds used to limit waits for output operations to complete. If a
send operation has blocked for this much time, it returns with a partial
count or with the error EWOULDBLOCK if no data were sent. In the current
implementation, this timer is restarted each time additional data are
delivered to the protocol, implying that the limit applies to output por-
tions ranging in size from the low-water mark to the high-water mark for
output.
SO_RCVTIMEO is an option to set a timeout value for input operations. It
accepts a struct timeval parameter with the number of seconds and
microseconds used to limit waits for input operations to complete. In
the current implementation, this timer is restarted each time additional
data are received by the protocol, and thus the limit is in effect an
inactivity timer. If a receive operation has been blocked for this much
time without receiving additional data, it returns with a short count or
with the error EWOULDBLOCK if no data were received. The struct timeval
parameter must represent a positive time interval; otherwise,
setsockopt() returns with the error EDOM.
SO_NOSIGPIPE is an option that prevents SIGPIPE from being raised when a
write fails on a socket to which there is no reader; instead, the write
to the socket returns with the error EPIPE when there is no reader.
Finally, SO_TYPE and SO_ERROR are options used only with getsockopt().
SO_TYPE returns the type of the socket, such as SOCK_STREAM; it is useful
for servers that inherit sockets on startup. SO_ERROR returns any pend-
ing error on the socket and clears the error status. It may be used to
check for asynchronous errors on connected datagram sockets or for other
asynchronous errors.
RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the
value -1 is returned and the global variable errno is set to indicate the
error.
ERRORS
The getsockopt() and setsockopt() system calls will succeed unless:
[EBADF] The argument socket is not a valid file descriptor.
[EFAULT] The address pointed to by option_value is not in a
valid part of the process address space. For
getsockopt(), this error may also be returned if
option_len is not in a valid part of the process
address space.
[EINVAL] The option is invalid at the level indicated.
[ENOBUFS] Insufficient memory buffers are available.
[ENOPROTOOPT] The option is unknown at the level indicated.
[ENOTSOCK] The argument socket is not a socket (e.g., a plain
file).
The setsockopt() system call will succeed unless:
[EDOM] The argument option_value is out of bounds.
[EISCONN] socket is already connected and a specified option
cannot be set while this is the case.
LEGACY SYNOPSIS
#include <sys/types.h>
#include <sys/socket.h>
The include file <sys/types.h> is necessary.
SEE ALSO
ioctl(2), socket(2), getprotoent(3), protocols(5)
#6
多使用man命令查看帮助，或者google搜索man setsockopt
#7
刚才看了一下代码：
在accept前 已经setsockopt 了，如下：
int keepalive = 1;
if( setsockopt( fd_socket, SOL_SOCKET, SO_KEEPALIVE,
(char*)&keepalive, sizeof(keepalive)) != 0)
{
在accept前 已经setsockopt 了，如下：
int keepalive = 1;
if( setsockopt( fd_socket, SOL_SOCKET, SO_KEEPALIVE,
(char*)&keepalive, sizeof(keepalive)) != 0)
{
#8
冒昧的说一下
你这种服务器模式我还是第一次看到
我不是太清楚内核的accept是怎么实现的
但是，直觉上，同一个socket有多个线程去accept
假设内核允许这么做，那么应该把监听到的连接分配给哪个线程呢？
分配给所有线程，逻辑上通不过
如果按照某种算法分配给某一个线程
那与单线程accept有何区别？
我所说的单线程accept是指这样的服务器模式
即在主线程创建socket，listen，然后循环accept
当有连接进来的时候，再用多线程去recv并处理逻辑
这是经典的thread-per-connection
你这种服务器模式我还是第一次看到
我不是太清楚内核的accept是怎么实现的
但是，直觉上，同一个socket有多个线程去accept
假设内核允许这么做，那么应该把监听到的连接分配给哪个线程呢？
分配给所有线程，逻辑上通不过
如果按照某种算法分配给某一个线程
那与单线程accept有何区别？
我所说的单线程accept是指这样的服务器模式
即在主线程创建socket，listen，然后循环accept
当有连接进来的时候，再用多线程去recv并处理逻辑
这是经典的thread-per-connection
#9
http://careerman.blog.ccidnet.com/blog-htm-do-showone-uid-12026-type-blog-itemid-186476.html
看看setsockopt处理常见错误先吧
看看setsockopt处理常见错误先吧
#10
这种模式 我也觉得奇怪，但是之前的同事写。在sco下运行都正常的
#11
我才仔细看代码，这个代码肯定有问题。
fork是创建子进程，子进程会继承父进程资源、环境，暂且认为socket描述符也能继承（我没有考究），那么多进程同时监听一个描述符？也就是同一个端口号？因为accept在每一个进程内，不知道，在来了一个请求的时候，是不是会有多个进程响应，而造成Resource temporarily unavailable（资源暂时不可用）。
正确的方法是在主进程里accept，然后创建子进程处理请求。
#12
多线程也是一样，在主线程中accept，在子线程中处理请求。
#13
多谢了！
但在sco下运行时正常的，不知道何解
但在sco下运行时正常的，不知道何解
#14
不过在accept 前，已经设置了阻塞。但好像无效。。。。
#15
这个不能代表程序就没问题的，可能sco的内核对这种情况有特殊的处理呢……
#16
《unix网络编程》上将到这种处理方式了：TCP预先派生子进程服务器程序，accept在子进程处理....
#17
我想说的是，fork的子进程会不会也执行fork，所以创建的进程不是5个，而是31个吧~~
#1
you must use setsockopt function to control the socket's operation:
SO_REUSEADDR
SO_KEEPALIVE
SO_LINGER
SO_RCVTIMEO
SO_SNDTIMEO
SO_REUSEADDR
SO_KEEPALIVE
SO_LINGER
SO_RCVTIMEO
SO_SNDTIMEO
#2
帮顶~
#3
请问datacodebugs ；在哪设置?因为本人初次接触 socket编程，不太熟悉
#4
NAME
getsockopt, setsockopt -- get and set options on sockets
SYNOPSIS
#include <sys/socket.h>
int
getsockopt(int socket, int level, int option_name,
void *restrict option_value, socklen_t *restrict option_len);
int
setsockopt(int socket, int level, int option_name,
const void *option_value, socklen_t option_len);
DESCRIPTION
Getsockopt() and setsockopt() manipulate the options associated with a
socket. Options may exist at multiple protocol levels; they are always
present at the uppermost ``socket'' level.
When manipulating socket options the level at which the option resides
and the name of the option must be specified. To manipulate options at
the socket level, level is specified as SOL_SOCKET. To manipulate
options at any other level the protocol number of the appropriate proto-
col controlling the option is supplied. For example, to indicate that an
option is to be interpreted by the TCP protocol, level should be set to
the protocol number of TCP; see getprotoent(3).
The parameters option_value and option_len are used to access option val-
ues for setsockopt(). For getsockopt() they identify a buffer in which
the value for the requested option(s) are to be returned. For
getsockopt(), option_len is a value-result parameter, initially contain-
ing the size of the buffer pointed to by option_value, and modified on
return to indicate the actual size of the value returned. If no option
value is to be supplied or returned, option_value may be NULL.
option_name and any specified options are passed uninterpreted to the
appropriate protocol module for interpretation. The include file
<sys/socket.h> contains definitions for socket level options, described
below. Options at other protocol levels vary in format and name; consult
the appropriate entries in section 4 of the manual.
Most socket-level options utilize an int parameter for option_value. For
setsockopt(), the parameter should be non-zero to enable a boolean
option, or zero if the option is to be disabled. SO_LINGER uses a struct
linger parameter, defined in <sys/socket.h>, which specifies the desired
state of the option and the linger interval (see below). SO_SNDTIMEO and
SO_RCVTIMEO use a struct timeval parameter, defined in <sys/time.h>.
The following options are recognized at the socket level. Except as
noted, each may be examined with getsockopt() and set with setsockopt().
SO_DEBUG enables recording of debugging information
SO_REUSEADDR enables local address reuse
SO_REUSEPORT enables duplicate address and port bindings
SO_KEEPALIVE enables keep connections alive
SO_DONTROUTE enables routing bypass for outgoing messages
SO_LINGER linger on close if data present
SO_BROADCAST enables permission to transmit broadcast messages
SO_OOBINLINE enables reception of out-of-band data in band
SO_SNDBUF set buffer size for output
SO_RCVBUF set buffer size for input
SO_SNDLOWAT set minimum count for output
SO_RCVLOWAT set minimum count for input
SO_SNDTIMEO set timeout value for output
SO_RCVTIMEO set timeout value for input
SO_TYPE get the type of the socket (get only)
SO_ERROR get and clear error on the socket (get only)
SO_NOSIGPIPE do not generate SIGPIPE, instead return EPIPE
SO_DEBUG enables debugging in the underlying protocol modules.
SO_REUSEADDR indicates that the rules used in validating addresses sup-
plied in a bind(2) call should allow reuse of local addresses.
SO_REUSEPORT allows completely duplicate bindings by multiple processes
if they all set SO_REUSEPORT before binding the port. This option per-
mits multiple instances of a program to each receive UDP/IP multicast or
broadcast datagrams destined for the bound port. SO_KEEPALIVE enables
the periodic transmission of messages on a connected socket. Should the
connected party fail to respond to these messages, the connection is con-
sidered broken and processes using the socket are notified via a SIGPIPE
signal when attempting to send data. SO_DONTROUTE indicates that outgo-
ing messages should bypass the standard routing facilities. Instead,
messages are directed to the appropriate network interface according to
the network portion of the destination address.
getsockopt, setsockopt -- get and set options on sockets
SYNOPSIS
#include <sys/socket.h>
int
getsockopt(int socket, int level, int option_name,
void *restrict option_value, socklen_t *restrict option_len);
int
setsockopt(int socket, int level, int option_name,
const void *option_value, socklen_t option_len);
DESCRIPTION
Getsockopt() and setsockopt() manipulate the options associated with a
socket. Options may exist at multiple protocol levels; they are always
present at the uppermost ``socket'' level.
When manipulating socket options the level at which the option resides
and the name of the option must be specified. To manipulate options at
the socket level, level is specified as SOL_SOCKET. To manipulate
options at any other level the protocol number of the appropriate proto-
col controlling the option is supplied. For example, to indicate that an
option is to be interpreted by the TCP protocol, level should be set to
the protocol number of TCP; see getprotoent(3).
The parameters option_value and option_len are used to access option val-
ues for setsockopt(). For getsockopt() they identify a buffer in which
the value for the requested option(s) are to be returned. For
getsockopt(), option_len is a value-result parameter, initially contain-
ing the size of the buffer pointed to by option_value, and modified on
return to indicate the actual size of the value returned. If no option
value is to be supplied or returned, option_value may be NULL.
option_name and any specified options are passed uninterpreted to the
appropriate protocol module for interpretation. The include file
<sys/socket.h> contains definitions for socket level options, described
below. Options at other protocol levels vary in format and name; consult
the appropriate entries in section 4 of the manual.
Most socket-level options utilize an int parameter for option_value. For
setsockopt(), the parameter should be non-zero to enable a boolean
option, or zero if the option is to be disabled. SO_LINGER uses a struct
linger parameter, defined in <sys/socket.h>, which specifies the desired
state of the option and the linger interval (see below). SO_SNDTIMEO and
SO_RCVTIMEO use a struct timeval parameter, defined in <sys/time.h>.
The following options are recognized at the socket level. Except as
noted, each may be examined with getsockopt() and set with setsockopt().
SO_DEBUG enables recording of debugging information
SO_REUSEADDR enables local address reuse
SO_REUSEPORT enables duplicate address and port bindings
SO_KEEPALIVE enables keep connections alive
SO_DONTROUTE enables routing bypass for outgoing messages
SO_LINGER linger on close if data present
SO_BROADCAST enables permission to transmit broadcast messages
SO_OOBINLINE enables reception of out-of-band data in band
SO_SNDBUF set buffer size for output
SO_RCVBUF set buffer size for input
SO_SNDLOWAT set minimum count for output
SO_RCVLOWAT set minimum count for input
SO_SNDTIMEO set timeout value for output
SO_RCVTIMEO set timeout value for input
SO_TYPE get the type of the socket (get only)
SO_ERROR get and clear error on the socket (get only)
SO_NOSIGPIPE do not generate SIGPIPE, instead return EPIPE
SO_DEBUG enables debugging in the underlying protocol modules.
SO_REUSEADDR indicates that the rules used in validating addresses sup-
plied in a bind(2) call should allow reuse of local addresses.
SO_REUSEPORT allows completely duplicate bindings by multiple processes
if they all set SO_REUSEPORT before binding the port. This option per-
mits multiple instances of a program to each receive UDP/IP multicast or
broadcast datagrams destined for the bound port. SO_KEEPALIVE enables
the periodic transmission of messages on a connected socket. Should the
connected party fail to respond to these messages, the connection is con-
sidered broken and processes using the socket are notified via a SIGPIPE
signal when attempting to send data. SO_DONTROUTE indicates that outgo-
ing messages should bypass the standard routing facilities. Instead,
messages are directed to the appropriate network interface according to
the network portion of the destination address.
#5
SO_LINGER controls the action taken when unsent messages are queued on
socket and a close(2) is performed. If the socket promises reliable
delivery of data and SO_LINGER is set, the system will block the process
on the close attempt until it is able to transmit the data or until it
decides it is unable to deliver the information (a timeout period, termed
the linger interval, is specified in the setsockopt() call when SO_LINGER
is requested). If SO_LINGER is disabled and a close is issued, the sys-
tem will process the close in a manner that allows the process to con-
tinue as quickly as possible.
The option SO_BROADCAST requests permission to send broadcast datagrams
on the socket. Broadcast was a privileged operation in earlier versions
of the system. With protocols that support out-of-band data, the
SO_OOBINLINE option requests that out-of-band data be placed in the nor-
mal data input queue as received; it will then be accessible with recv or
read calls without the MSG_OOB flag. Some protocols always behave as if
this option is set. SO_SNDBUF and SO_RCVBUF are options to adjust the
normal buffer sizes allocated for output and input buffers, respectively.
The buffer size may be increased for high-volume connections, or may be
decreased to limit the possible backlog of incoming data. The system
places an absolute limit on these values.
SO_SNDLOWAT is an option to set the minimum count for output operations.
Most output operations process all of the data supplied by the call,
delivering data to the protocol for transmission and blocking as neces-
sary for flow control. Nonblocking output operations will process as
much data as permitted (subject to flow control) without blocking, but
will process no data if flow control does not allow the smaller of the
low-water mark value or the entire request to be processed. A select(2)
operation testing the ability to write to a socket will return true only
if the low-water mark amount could be processed. The default value for
SO_SNDLOWAT is set to a convenient size for network efficiency, often
1024.
SO_RCVLOWAT is an option to set the minimum count for input operations.
In general, receive calls will block until any (non-zero) amount of data
is received, then return with the smaller of the amount available or the
amount requested. The default value for SO_RCVLOWAT is 1. If
SO_RCVLOWAT is set to a larger value, blocking receive calls normally
wait until they have received the smaller of the low-water mark value or
the requested amount. Receive calls may still return less than the low-
water mark if an error occurs, a signal is caught, or the type of data
next in the receive queue is different than that returned.
SO_SNDTIMEO is an option to set a timeout value for output operations.
It accepts a struct timeval parameter with the number of seconds and
microseconds used to limit waits for output operations to complete. If a
send operation has blocked for this much time, it returns with a partial
count or with the error EWOULDBLOCK if no data were sent. In the current
implementation, this timer is restarted each time additional data are
delivered to the protocol, implying that the limit applies to output por-
tions ranging in size from the low-water mark to the high-water mark for
output.
SO_RCVTIMEO is an option to set a timeout value for input operations. It
accepts a struct timeval parameter with the number of seconds and
microseconds used to limit waits for input operations to complete. In
the current implementation, this timer is restarted each time additional
data are received by the protocol, and thus the limit is in effect an
inactivity timer. If a receive operation has been blocked for this much
time without receiving additional data, it returns with a short count or
with the error EWOULDBLOCK if no data were received. The struct timeval
parameter must represent a positive time interval; otherwise,
setsockopt() returns with the error EDOM.
SO_NOSIGPIPE is an option that prevents SIGPIPE from being raised when a
write fails on a socket to which there is no reader; instead, the write
to the socket returns with the error EPIPE when there is no reader.
Finally, SO_TYPE and SO_ERROR are options used only with getsockopt().
SO_TYPE returns the type of the socket, such as SOCK_STREAM; it is useful
for servers that inherit sockets on startup. SO_ERROR returns any pend-
ing error on the socket and clears the error status. It may be used to
check for asynchronous errors on connected datagram sockets or for other
asynchronous errors.
RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the
value -1 is returned and the global variable errno is set to indicate the
error.
ERRORS
The getsockopt() and setsockopt() system calls will succeed unless:
[EBADF] The argument socket is not a valid file descriptor.
[EFAULT] The address pointed to by option_value is not in a
valid part of the process address space. For
getsockopt(), this error may also be returned if
option_len is not in a valid part of the process
address space.
[EINVAL] The option is invalid at the level indicated.
[ENOBUFS] Insufficient memory buffers are available.
[ENOPROTOOPT] The option is unknown at the level indicated.
[ENOTSOCK] The argument socket is not a socket (e.g., a plain
file).
The setsockopt() system call will succeed unless:
[EDOM] The argument option_value is out of bounds.
[EISCONN] socket is already connected and a specified option
cannot be set while this is the case.
LEGACY SYNOPSIS
#include <sys/types.h>
#include <sys/socket.h>
The include file <sys/types.h> is necessary.
SEE ALSO
ioctl(2), socket(2), getprotoent(3), protocols(5)
socket and a close(2) is performed. If the socket promises reliable
delivery of data and SO_LINGER is set, the system will block the process
on the close attempt until it is able to transmit the data or until it
decides it is unable to deliver the information (a timeout period, termed
the linger interval, is specified in the setsockopt() call when SO_LINGER
is requested). If SO_LINGER is disabled and a close is issued, the sys-
tem will process the close in a manner that allows the process to con-
tinue as quickly as possible.
The option SO_BROADCAST requests permission to send broadcast datagrams
on the socket. Broadcast was a privileged operation in earlier versions
of the system. With protocols that support out-of-band data, the
SO_OOBINLINE option requests that out-of-band data be placed in the nor-
mal data input queue as received; it will then be accessible with recv or
read calls without the MSG_OOB flag. Some protocols always behave as if
this option is set. SO_SNDBUF and SO_RCVBUF are options to adjust the
normal buffer sizes allocated for output and input buffers, respectively.
The buffer size may be increased for high-volume connections, or may be
decreased to limit the possible backlog of incoming data. The system
places an absolute limit on these values.
SO_SNDLOWAT is an option to set the minimum count for output operations.
Most output operations process all of the data supplied by the call,
delivering data to the protocol for transmission and blocking as neces-
sary for flow control. Nonblocking output operations will process as
much data as permitted (subject to flow control) without blocking, but
will process no data if flow control does not allow the smaller of the
low-water mark value or the entire request to be processed. A select(2)
operation testing the ability to write to a socket will return true only
if the low-water mark amount could be processed. The default value for
SO_SNDLOWAT is set to a convenient size for network efficiency, often
1024.
SO_RCVLOWAT is an option to set the minimum count for input operations.
In general, receive calls will block until any (non-zero) amount of data
is received, then return with the smaller of the amount available or the
amount requested. The default value for SO_RCVLOWAT is 1. If
SO_RCVLOWAT is set to a larger value, blocking receive calls normally
wait until they have received the smaller of the low-water mark value or
the requested amount. Receive calls may still return less than the low-
water mark if an error occurs, a signal is caught, or the type of data
next in the receive queue is different than that returned.
SO_SNDTIMEO is an option to set a timeout value for output operations.
It accepts a struct timeval parameter with the number of seconds and
microseconds used to limit waits for output operations to complete. If a
send operation has blocked for this much time, it returns with a partial
count or with the error EWOULDBLOCK if no data were sent. In the current
implementation, this timer is restarted each time additional data are
delivered to the protocol, implying that the limit applies to output por-
tions ranging in size from the low-water mark to the high-water mark for
output.
SO_RCVTIMEO is an option to set a timeout value for input operations. It
accepts a struct timeval parameter with the number of seconds and
microseconds used to limit waits for input operations to complete. In
the current implementation, this timer is restarted each time additional
data are received by the protocol, and thus the limit is in effect an
inactivity timer. If a receive operation has been blocked for this much
time without receiving additional data, it returns with a short count or
with the error EWOULDBLOCK if no data were received. The struct timeval
parameter must represent a positive time interval; otherwise,
setsockopt() returns with the error EDOM.
SO_NOSIGPIPE is an option that prevents SIGPIPE from being raised when a
write fails on a socket to which there is no reader; instead, the write
to the socket returns with the error EPIPE when there is no reader.
Finally, SO_TYPE and SO_ERROR are options used only with getsockopt().
SO_TYPE returns the type of the socket, such as SOCK_STREAM; it is useful
for servers that inherit sockets on startup. SO_ERROR returns any pend-
ing error on the socket and clears the error status. It may be used to
check for asynchronous errors on connected datagram sockets or for other
asynchronous errors.
RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the
value -1 is returned and the global variable errno is set to indicate the
error.
ERRORS
The getsockopt() and setsockopt() system calls will succeed unless:
[EBADF] The argument socket is not a valid file descriptor.
[EFAULT] The address pointed to by option_value is not in a
valid part of the process address space. For
getsockopt(), this error may also be returned if
option_len is not in a valid part of the process
address space.
[EINVAL] The option is invalid at the level indicated.
[ENOBUFS] Insufficient memory buffers are available.
[ENOPROTOOPT] The option is unknown at the level indicated.
[ENOTSOCK] The argument socket is not a socket (e.g., a plain
file).
The setsockopt() system call will succeed unless:
[EDOM] The argument option_value is out of bounds.
[EISCONN] socket is already connected and a specified option
cannot be set while this is the case.
LEGACY SYNOPSIS
#include <sys/types.h>
#include <sys/socket.h>
The include file <sys/types.h> is necessary.
SEE ALSO
ioctl(2), socket(2), getprotoent(3), protocols(5)
#6
多使用man命令查看帮助，或者google搜索man setsockopt
#7
刚才看了一下代码：
在accept前 已经setsockopt 了，如下：
int keepalive = 1;
if( setsockopt( fd_socket, SOL_SOCKET, SO_KEEPALIVE,
(char*)&keepalive, sizeof(keepalive)) != 0)
{
在accept前 已经setsockopt 了，如下：
int keepalive = 1;
if( setsockopt( fd_socket, SOL_SOCKET, SO_KEEPALIVE,
(char*)&keepalive, sizeof(keepalive)) != 0)
{
#8
冒昧的说一下
你这种服务器模式我还是第一次看到
我不是太清楚内核的accept是怎么实现的
但是，直觉上，同一个socket有多个线程去accept
假设内核允许这么做，那么应该把监听到的连接分配给哪个线程呢？
分配给所有线程，逻辑上通不过
如果按照某种算法分配给某一个线程
那与单线程accept有何区别？
我所说的单线程accept是指这样的服务器模式
即在主线程创建socket，listen，然后循环accept
当有连接进来的时候，再用多线程去recv并处理逻辑
这是经典的thread-per-connection
你这种服务器模式我还是第一次看到
我不是太清楚内核的accept是怎么实现的
但是，直觉上，同一个socket有多个线程去accept
假设内核允许这么做，那么应该把监听到的连接分配给哪个线程呢？
分配给所有线程，逻辑上通不过
如果按照某种算法分配给某一个线程
那与单线程accept有何区别？
我所说的单线程accept是指这样的服务器模式
即在主线程创建socket，listen，然后循环accept
当有连接进来的时候，再用多线程去recv并处理逻辑
这是经典的thread-per-connection
#9
http://careerman.blog.ccidnet.com/blog-htm-do-showone-uid-12026-type-blog-itemid-186476.html
看看setsockopt处理常见错误先吧
看看setsockopt处理常见错误先吧
#10
这种模式 我也觉得奇怪，但是之前的同事写。在sco下运行都正常的
#11
我才仔细看代码，这个代码肯定有问题。
fork是创建子进程，子进程会继承父进程资源、环境，暂且认为socket描述符也能继承（我没有考究），那么多进程同时监听一个描述符？也就是同一个端口号？因为accept在每一个进程内，不知道，在来了一个请求的时候，是不是会有多个进程响应，而造成Resource temporarily unavailable（资源暂时不可用）。
正确的方法是在主进程里accept，然后创建子进程处理请求。
#12
多线程也是一样，在主线程中accept，在子线程中处理请求。
#13
多谢了！
但在sco下运行时正常的，不知道何解
但在sco下运行时正常的，不知道何解
#14
不过在accept 前，已经设置了阻塞。但好像无效。。。。
#15
这个不能代表程序就没问题的，可能sco的内核对这种情况有特殊的处理呢……
#16
《unix网络编程》上将到这种处理方式了：TCP预先派生子进程服务器程序，accept在子进程处理....
#17
我想说的是，fork的子进程会不会也执行fork，所以创建的进程不是5个，而是31个吧~~