Interested to Buy Any Domain ? << Click Here >> for more details...
Why do not my sockets close?
- 1 Answers
- 2323 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 can I put a timeout on connect()?
When should I use shutdown()?
How do I use TCP_NODELAY?
What is difference between socket () and serversocket () class?
When should I use UDP instead of TCP?
How does unix socket work?
What is the purpose of socket?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
How can I force a socket to send the data in its buffer?
How can I bind() to a port number < 1024?
What is a socket set used for?
Is socket a hardware or software?
Unix Commands 
