Sponsored Content
Top Forums Programming Closing Socket Gracefully Solaris Post 302600353 by mr_deb on Tuesday 21st of February 2012 01:01:33 AM
Old 02-21-2012
Closing Socket Gracefully Solaris

Hi All

I am creating one client socket with SO_LINGER option Disabled

Code:
   struct linger LingerState = {0, 0};
   if (setsockopt(_hSocketTCP, SOL_SOCKET,
				   SO_LINGER, (const char *) &LingerState, sizeof(struct linger)) == -1)
	{
		cout<<"Cannot set linger to 0 for socket"<<endl
	}

And for Closing the socket I am using following API
Code:
               shutdown(_hSocketTCP, 2);
		close(_hSocketTCP);

Now Problem is during closing when client Send FIN_1 to server ,Server also send ACK for it .But as Linger state is disable client has already closed the socket with out waiting for the ACK message from server. As a result Server didnt get the FIN_2 message and its not able to understand that client has close the socket.So whenever its tries to send next message its(server) getting error Broken PIPE.

So Just want to know if we Enable SO_LINGER option will it fix the problem.

Last edited by mr_deb; 02-21-2012 at 02:07 AM..
 

9 More Discussions You Might Find Interesting

1. Programming

Socket Programming socket

Hello, I actually try to make client-server program. I'm using SCO OpenServer Release 5.0.0 and when I try to compile my code (by TELNET) I've got this error : I'm just using this simple code : and I get the same error if I use : If someone can help me, Thanks (2 Replies)
Discussion started by: soshell
2 Replies

2. Shell Programming and Scripting

Shell script not exiting Gracefully

Hi we are seeing strange behaviour , when we execute shell script it is successfully executing but it's PID is still hanging when we see ps -ef | grep script1.ksh until we do Kill <PID> $script1.ksh $ $ ps -ef | grep script1.ksh user1 249996 1 0 10:48:40 pts/1 0:00... (5 Replies)
Discussion started by: smithK
5 Replies

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

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

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

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

7. IP Networking

Closing the socket

Hi, I have a question on closing the listen socket in server. In the application I am working, the server is continously receiving requests from the client in its master socket to handle each request. There is an option to shutdown the server process. In this case do I need to explicitly close... (1 Reply)
Discussion started by: naan
1 Replies

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

9. Post Here to Contact Site Administrators and Moderators

Closing thread

Hi, I guess, users do not have rights to close a thread. Please close thread 'Small automation' as it is resolved. Regards, snjksh (1 Reply)
Discussion started by: snjksh
1 Replies
getsockopt(3SOCKET)					     Sockets Library Functions					       getsockopt(3SOCKET)

NAME
getsockopt, setsockopt - get and set options on sockets SYNOPSIS
cc [ flag ... ] file ... -lsocket -lnsl [ library ... ] #include <sys/types.h> #include <sys/socket.h> int getsockopt(int s, int level, int optname, void *optval, int *optlen); int setsockopt(int s, int level, int optname, const void *optval, int optlen); DESCRIPTION
getsockopt() and setsockopt() manipulate 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, level is the protocol number of the pro- tocol that controls the option. For example, to indicate that an option is to be interpreted by the TCP protocol, level is set to the TCP protocol number . See getprotobyname(3SOCKET). The parameters optval and optlen are used to access option values for setsockopt(). For getsockopt(), they identify a buffer in which the value(s) for the requested option(s) are to be returned. For getsockopt(), optlen is a value-result parameter, initially containing the size of the buffer pointed to by optval, and modified on return to indicate the actual size of the value returned. Use a 0 optval if no option value is to be supplied or returned. optname and any specified options are passed uninterpreted to the appropriate protocol module for interpretation. The include file <sys/socket.h> contains definitions for the socket-level options described below. Options at other protocol levels vary in format and name. Most socket-level options take an int for optval. For setsockopt(), the optval 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 that specifies the desired state of the option and the linger interval. struct linger is defined in <sys/socket.h>. struct linger contains the following members: l_onoff on = 1/off = 0 l_linger linger time, in seconds The following options are recognized at the socket level. Except as noted, each may be examined with getsockopt() and set with setsock- opt(). SO_DEBUG enable/disable recording of debugging information SO_REUSEADDR enable/disable local address reuse SO_KEEPALIVE enable/disable keep connections alive SO_DONTROUTE enable/disable routing bypass for outgoing messages SO_LINGER linger on close if data is present SO_BROADCAST enable/disable permission to transmit broadcast messages SO_OOBINLINE enable/disable reception of out-of-band data in band SO_SNDBUF set buffer size for output SO_RCVBUF set buffer size for input SO_DGRAM_ERRIND application wants delayed error SO_TYPE get the type of the socket (get only) SO_ERROR get and clear error on the socket (get only) SO_DEBUG enables debugging in the underlying protocol modules. SO_REUSEADDR indicates that the rules used in validating addresses supplied in a bind(3SOCKET) call should allow reuse of local addresses. SO_KEEPALIVE enables the periodic transmission of messages on a connected socket. If the connected party fails to respond to these messages, the connection is considered broken and threads using the socket are notified using a SIGPIPE signal. SO_DONTROUTE indicates that outgoing messages should bypass the standard routing facilities. Instead, mes- sages are directed to the appropriate network interface according to the network portion of the destination address. SO_LINGER controls the action taken when unsent messages are queued on a socket and a close(2) is performed. If the socket promises reli- able delivery of data and SO_LINGER is set, the system will block the thread 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 system will process the close() in a manner that allows the thread to continue as quickly as possible. The option SO_BROADCAST requests permission to send broadcast datagrams on the socket. With protocols that support out-of-band data, the SO_OOBINLINE option requests that out-of-band data be placed in the normal data input queue as received; it will then be accessible with recv() or read() calls without the MSG_OOB flag. SO_SNDBUF and SO_RCVBUF are options that 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 maximum buffer size for UDP is determined by the value of the ndd variable udp_max_buf. The maximum buffer size for TCP is determined the value of the ndd variable tcp_max_buf. Use the ndd(1M) utility to determine the current default values. See the Solaris Tunable Parameters Refer- ence Manual for information on setting the values of udp_max_buf and tcp_max_buf. By default, delayed errors (such as ICMP port unreachable packets) are returned only for connected datagram sockets. SO_DGRAM_ERRIND makes it possible to receive errors for datagram sockets that are not connected. When this option is set, certain delayed errors received after completion of a sendto() or sendmsg() operation will cause a subsequent sendto() or sendmsg() operation using the same destination address (to parameter) to fail with the appropriate error. See send(3SOCKET). Finally, SO_TYPE and SO_ERROR are options used only with getsockopt(). SO_TYPE returns the type of the socket, for example, SOCK_STREAM. It is useful for servers that inherit sockets on startup. SO_ERROR returns any pending 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
If successful, getsockopt() and setsockopt() return 0; otherwise, the functions return -1 and set errno to indicate the error. ERRORS
The getsockopt() and setsockopt() calls succeed unless: EBADF The argument s is not a valid file descriptor. ENOMEM There was insufficient memory available for the operation to complete. ENOPROTOOPT The option is unknown at the level indicated. ENOSR There were insufficient STREAMS resources available for the operation to complete. ENOTSOCK The argument s is not a socket. ENOBUFS SO_SNDBUF or SO_RCVBUF exceeds a system limit. EINVAL Invalid length for IP_OPTIONS. EHOSTUNREACH Invalid address for IP_MULTICAST_IF. EINVAL Not a multicast address for IP_ADD_MEMBERSHIP and IP_DROP_MEMBERSHIP. EADDRNOTAVAIL Bad interface address for IP_ADD_MEMBERSHIP and IP_DROP_MEMBERSHIP. EADDRINUSE Address already joined for IP_ADD_MEMBERSHIP. ENOENT Address not joined for IP_DROP_MEMBERSHIP. EPERM No permissions. EINVAL The specified option is invalid at the specified socket level, or the socket has been shut down. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
ndd(1M), close(2), ioctl(2), read(2), bind(3SOCKET), getprotobyname(3SOCKET), recv(3SOCKET), send(3SOCKET), socket(3SOCKET), attributes(5) Solaris Tunable Parameters Reference Manual SunOS 5.10 1 Nov 2003 getsockopt(3SOCKET)
All times are GMT -4. The time now is 10:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy