Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / 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 |
Post New Answer View All Answers
What is a socket api?
How does unix socket work?
Why does the sockets buffer fill up sooner than expected?
What is the function of socket?
Is there any advantage to handling the signal, rather than just ignoring it and checking for the EPIPE error? Are there any useful parameters passed to the signal catching function?
What is difference between socket and websocket?
What pieces of information make up a socket?
What is the purpose of socket?
Can multiple clients connect to same socket?
What is a deep well socket?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
What is a socket address?
Is a socket a file?
What is a sae socket?
Can multiple sockets use the same port?
