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 are the pros/cons of select(), non-blocking I/O and SIGIO?
What is a socket connection?
Is tcp or unix socket faster?
How many sockets can a port have?
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 set used for?
Can a socket have multiple ports?
Where is the socket located?
What is the difference between SO_REUSEADDR and SO_REUSEPORT?
What is sae socket?
How can I tell when a socket is closed on the other end?
What is the function of socket?
What is a deep well socket?
What is the difference between a socket and a port?
How do unix sockets work?
