Interested to Buy Any Domain ? << Click Here >> for more details...
Why do not my sockets close?
- 1 Answers
- 2300 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 |
Why do not my sockets close?
How can I write a multi-homed server?
Are unix sockets faster than tcp?
Why do we need socket programming?
What exactly does SO_REUSEADDR do?
Can a single socket port be used for multiple applications?
How can I read only one character at a time?
What is a sae socket?
How do I get the port number for a given service?
What is the difference between SO_REUSEADDR and SO_REUSEPORT?
Where can a get a library for programming sockets?
How can I set the timeout for the connect() system call?
Unix Commands 
