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

I did set my kern.ipc.somaxconn kernel parameter to tweak the maximum backlog TCP size for incoming connections on my server. I'm now looking to read the current amount of request pending in this backlog.

I thought for a moment it was the number of connection in the state 'ESTABLISED' in the ouput of netstat, but I understood that requests being processed by the application could also be in this state.

Is there a file I have to read in the /proc/ filesystem, is it an option of netstat that I missed?

share|improve this question
up vote 2 down vote accepted

If I understand the question correctly, I believe you're referring to the Recv-Q and Send-Q numbers from netstat.

If these numbers are not near zero, there is a high probability that there is either something going wrong with hardware, or that you are saturating your link.

share|improve this answer
To clarify, Recv-Q: "The count of bytes not copied by the user program connected to this socket." and Send-Q: "The count of bytes not acknowledged by the remote host." (from the linux manual) – rakslice Dec 13 '11 at 20:41

TCP connection's data are 1st received into a buffer which lies in kernelspace. In that case Recv-Q is non-zero. And then if process calls read are copied into userpace. If not(the app is saturated), they will remain in the kernel buffer.

PS: are you using Linux or FreeBSD?

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.