Socket options


 
Thread Tools Search this Thread
Operating Systems Solaris Socket options
# 1  
Old 08-03-2010
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? Smilie

---------- Post updated at 03:50 PM ---------- Previous update was at 02:52 PM ----------

Found it ...

lsof -i -Tf

Another undocumented switch
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Ubuntu

Kernel boot options removed by fault, no boot options

Hello Everyone, First of all, I highly appreciate all Linux forum members and whole Linux community. http://forums.linuxmint.com/images/smilies/icon_wink.gif. I wish you the best for all of you ! I will try to be short and concise: I am using Linux Mint 10 for 2 months on 2 ws, and all went... (3 Replies)
Discussion started by: cdt
3 Replies

2. IP Networking

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)... (2 Replies)
Discussion started by: jake24
2 Replies

3. 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

4. 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

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. 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

7. 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

8. 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
Login or Register to Ask a Question
gen_udp(3erl)						     Erlang Module Definition						     gen_udp(3erl)

NAME
gen_udp - Interface to UDP sockets DESCRIPTION
The gen_udp module provides functions for communicating with sockets using the UDP protocol. DATA TYPES
ip_address() see inet(3erl) posix() see inet(3erl) socket() as returned by open/1,2 EXPORTS
open(Port) -> {ok, Socket} | {error, Reason} open(Port, Options) -> {ok, Socket} | {error, Reason} Types Port = 0..65535 Options = [Opt] Opt -- see below Socket = socket() Reason = posix() Associates a UDP port number ( Port ) with the calling process. The available options are: list : Received Packet is delivered as a list. binary : Received Packet is delivered as a binary. {ip, ip_address()} : If the host has several network interfaces, this option specifies which one to use. {fd, int()} : If a socket has somehow been opened without using gen_udp , use this option to pass the file descriptor for it. inet6 : Set up the socket for IPv6. inet : Set up the socket for IPv4. Opt : See inet:setopts/2 . The returned socket Socket is used to send packets from this port with send/4 . When UDP packets arrive at the opened port, they are delivered as messages: {udp, Socket, IP, InPortNo, Packet} Note that arriving UDP packets that are longer than the receive buffer option specifies, might be truncated without warning. IP and InPortNo define the address from which Packet came. Packet is a list of bytes if the option list was specified. Packet is a binary if the option binary was specified. Default value for the receive buffer option is {recbuf, 8192} . If Port == 0 , the underlying OS assigns a free UDP port, use inet:port/1 to retrieve it. send(Socket, Address, Port, Packet) -> ok | {error, Reason} Types Socket = socket() Address = string() | atom() | ip_address() Port = 0..65535 Packet = [char()] | binary() Reason = not_owner | posix() Sends a packet to the specified address and port. The Address argument can be either a hostname, or an IP address. recv(Socket, Length) -> {ok, {Address, Port, Packet}} | {error, Reason} recv(Socket, Length, Timeout) -> {ok, {Address, Port, Packet}} | {error, Reason} Types Socket = socket() Length = int() Address = ip_address() Port = 0..65535 Packet = [char()] | binary() Timeout = int() | infinity Reason = not_owner | posix() This function receives a packet from a socket in passive mode. The optional Timeout parameter specifies a timeout in milliseconds. The default value is infinity . controlling_process(Socket, Pid) -> ok Types Socket = socket() Pid = pid() Assigns a new controlling process Pid to Socket . The controlling process is the process which receives messages from the socket. close(Socket) -> ok | {error, Reason} Types Socket = socket() Reason = not_owner | posix() Closes a UDP socket. Ericsson AB kernel 2.14.3 gen_udp(3erl)