Interested to Buy Any Domain ? << Click Here >> for more details...
Why do not my sockets close?
- 1 Answers
- 2470 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?
What is a socket connection?
After the chroot(), calls to socket() are failing. Why?
What is sae socket?
Can a single socket port be used for multiple applications?
What exactly is a socket?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
What's the difference between impact sockets and regular sockets?
Can multiple sockets use the same port?
Why sockets are used?
What is the difference between SO_REUSEADDR and SO_REUSEPORT?
How are unix domain sockets implemented?
Unix Commands 
