Sponsored Content
Special Forums IP Networking Clarification - Setting socket options at the same time when socket is listening Post 302515051 by jake24 on Monday 18th of April 2011 11:28:57 PM
Old 04-19-2011
Clarification - Setting socket options at the same time when socket is listening

I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?

Following is the scenario:-

-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global) for an incoming connection request with select() and then executing accept(fd,...) when a connection request arrives.
-- Task 2 - is a task that receives config commands from console and manipulates internal structures in response to them. As part of a particular command, it sets an option on the same listen socket using setsockopt(fd,....)

The option must be set on the listen socket fd ONLY when intimated to do so via a console command.

Can someone please clarify if it is okay to perform setsockopt on a socket when the same is being used in a simultaneous accept() call in another task?
 

10 More Discussions You Might Find Interesting

1. IP Networking

socket options

Hello there The socket option IP_OPTIONS returns an integer value, supposed to be the contents of the IP header. Could you please help me out to interpret those values. ThankYou. (1 Reply)
Discussion started by: hufs375
1 Replies

2. Programming

socket problems with cc compile options???

Hi there, a newbie as far as compiling c. I have a problem, I've ported a fairly simple perl socket program over to c. I compiled it as follows cc simplesocket.c -lsocket -lnsl compiles great, no errors. When I launch it from the command line, it works great!!!! However, if I... (5 Replies)
Discussion started by: googling2000
5 Replies

3. UNIX for Dummies Questions & Answers

Checking who is listening on a Unix Domain Socket

Hi all, I'm writing a kernel module and part of it involves controlling IPCs between processes. My problem is when a process tries to connect to a Unix domain socket, the only identifying information of the socket it supplies (that I can see, anyway) is the special pathname of the socket. From... (0 Replies)
Discussion started by: blank87
0 Replies

4. UNIX for Advanced & Expert Users

connect problem for sctp socket (ipv6 socket) - Runtime fail Invalid Arguments

Hi, I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime. To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies

5. Programming

which socket should socket option on be set

Hi all, On the server side, one socket is used for listening, the others are used for communicating with the client. My question is: if i want to set option for socket, which socket should be set on? If either can be set, what's the different? Again, what's the different if set option... (1 Reply)
Discussion started by: blademan100
1 Replies

6. Programming

socket function to read a webpage (socket.h)

Why does this socket function only read the first 1440 chars of the stream. Why not the whole stream ? I checked it with gdm and valgrind and everything seems correct... #include <stdio.h> #include <stdlib.h> #include <sys/types.h> #include <sys/stat.h> #include <string.h> #include... (3 Replies)
Discussion started by: cyler
3 Replies

7. Programming

Error with socket operation on non-socket

Dear Experts, i am compiling my code in suse 4.1 which is compiling fine, but at runtime it is showing me for socket programming error no 88 as i searched in errno.h it is telling me socket operation on non socket, what is the meaning of this , how to deal with this error , please... (1 Reply)
Discussion started by: vin_pll
1 Replies

8. Solaris

Socket options

Hi everyone, Question for gurus: Is there a way for us to determine the options used by a socket? I basically want to know if SO_KEEPALIVE is enabled on a socket to know if the tcp_keepalive_abort_interval parameter will be used by that connection. Was I clear enough? :confused: ... (0 Replies)
Discussion started by: plmachiavel
0 Replies

9. Red Hat

RHEL5.5 Socket Timeout Setting

Is there a Linux tunable to reduce the amount of time a socket waits before considering the remote side dead? Its the same senario when you try to telnet to a dead machine, telnet sits and waits for ~30seconds, before the socket timer expires and cancels the request. (5 Replies)
Discussion started by: mrmurdock
5 Replies

10. Shell Programming and Scripting

Is my Socket Free or Listening

Hi, bash-3.2$ uname -a Linux mymac 2.6.18-409.el5 #1 SMP Fri Feb 12 06:37:28 EST 2016 x86_64 x86_64 x86_64 GNU/Linux bash-3.2$ telnet 10.12.228.40 13900 Trying 10.12.228.40... telnet: connect to address 10.12.228.40: Connection refused bash-3.2$ telnet 10.12.228.40 23900 Trying... (2 Replies)
Discussion started by: mohtashims
2 Replies
LISTEN(2)						      BSD System Calls Manual							 LISTEN(2)

NAME
listen -- listen for connections on a socket SYNOPSIS
#include <sys/socket.h> int listen(int s, int backlog); DESCRIPTION
To accept connections, a socket is first created with socket(2), a willingness to accept incoming connections and a queue limit for incoming connections are specified with listen(), and then the connections are accepted with accept(2). The listen() call applies only to sockets of type SOCK_STREAM or SOCK_SEQPACKET. The backlog parameter defines the maximum length the queue of pending connections may grow to. If a connection request arrives with the queue full the client may receive an error with an indication of ECONNREFUSED, or, if the underlying protocol supports retransmission, the request may be ignored so that retries may succeed. RETURN VALUES
A 0 return value indicates success; -1 indicates an error. ERRORS
Listen() will fail if: [EBADF] The argument s is not a valid descriptor. [ENOTSOCK] The argument s is not a socket. [EOPNOTSUPP] The socket is not of a type that supports the operation listen(). SEE ALSO
accept(2), connect(2), socket(2) BUGS
The backlog is currently limited (silently) to 128. HISTORY
The listen() function call appeared in 4.2BSD. 4.2 Berkeley Distribution December 11, 1993 4.2 Berkeley Distribution
All times are GMT -4. The time now is 10:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy