Socket Programming of the CLOSE_WAIT SocketServer a procedure, there Client connecting overtime, use netstat-an |grep "PID>; check revealed a large CLOSE_WAIT state supposed to have this is normal, and this shows that closed remote socket. Server is awaiting the closure of the socket. But after a long time again to see, the situation remains the same, I feel some wrong. We ask prawn, CLOSE_WAIT longest duration can ah? The species is how the situation? The procedure is a multi-threaded, multi-process. Socket Programming of the CLOSE_WAIT A lot of CLOSE_WAIT more normal? Server-side in the process now? Clients continued to receive the signal link? Socket Programming of the CLOSE_WAIT CLOSE_WAIT initiative is the implementation of the closure of a state of the tcp end of the last experience, it closed SYN sent to the section of the terminal, waiting for the end of the ACK response section, the state is often kept 2MSL long time. Another is to enable Earlier this link might exist "fans sub-section" in the network completely disappeared. Prevent this section may be behind the "sober" to find the right path, but this time a new link is likely to recount, which had just closed links with the four elements of the same, then this section if it is to exist, what will happen? You may have to check the passive side of the closed proceedings, it made response to the SYN section. [ Closed window ]