Why do not my sockets close?
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 come I get address already in use from bind()?
Is socket a hardware or software?
What is a sae socket?
When will my application receive SIGPIPE?
Why do I get connection refused when the server is not running?
Can a socket have multiple ports?
What is the function of socket?
How can I bind() to a port number < 1024?
Why does it take so long to detect that the peer died?
Whats the difference between select() and poll()?
How are unix domain sockets implemented?
Why do we need socket programming?