Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

A general question about network connection on Linux : once a network connection goes into time_wait, is it still tied to the process ? Does it still use resources like say filehandle ?

Reason I ask is because once it goes into time_wait, lsof does not report it anymore. I guess that means that the network connection is no longer tied to the process and hence does not count against filehandle limit. Would like to confirm though.

share|improve this question
up vote 0 down vote accepted

Your guess is correct. If a connection enters the TIME_WAIT state, it means that the local side has closed the socket, therefore it has already stopped keeping the file descriptor in use.

It does, however, consume entries in the kernel TCP state table. There are a few tunables that you can look up in the tcp(7) man page. If you are only worried about the file descriptor count limit for a single process, however, it does not matter.

Please note that there is a duplicate question here, but I believe that the answer is incorrect.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.