Interested to Buy Any Domain ? << Click Here >> for more details...
Why do not my sockets close?
- 1 Answers
- 2390 Views
- I also Faced
- E-Mail Answers
Answer / chaitanya
When you issue the close() system call, you are closing your interface to the socket, not the socket itself. It is up to the kernel to close the socket. Sometimes, for really technical reasons, the socket is kept alive for a few minutes after you close it. It is normal, for example for the socket to go into a TIME_WAIT state, on the server side, for a few minutes. People have reported ranges from 20 seconds to 4 minutes to me. The official standard says that it should be 4 minutes. On my Linux system it is about 2 minutes. This is explained in great detail in ``2.7 Please explain the TIME_WAIT state.''.
| Is This Answer Correct ? | 0 Yes | 0 No |
How to find other end of unix socket connection?
over the socket? Is there a way to have a dynamic buffer? What does one do when one does not know how much information is coming?
What exactly is a socket?
How do I get the port number for a given service?
What's the difference between a socket and a port?
Where is the socket located?
How can I find the full hostname (FQDN) of the system I am running on?
How would I put my socket in non-blocking mode?
What is a socket file?
What's better 6pt or 12pt sockets?
Why do not my sockets close?
Why do we need socket programming?
Unix Commands 
