Why do not my sockets close?
- 1 Answers
- 2006 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 |
Where is the socket located?
What are the pros/cons of select(), non-blocking I/O and SIGIO?
How do Sockets Work?
Can multiple sockets use the same port?
How many sockets can a cpu have?
What is the difference between close() and shutdown()?
How can I force a socket to send the data in its buffer?
Explain the TIME_WAIT state.
What is sae socket?
How should I choose a port number for my server?
Is a socket a file?
What is a sae socket?
Unix Commands 
