From owner-freebsd-questions  Tue Sep 12 18:11:51 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id SAA20168
          for questions-outgoing; Tue, 12 Sep 1995 18:11:51 -0700
Received: from InfoWest.COM (InfoWest.COM [204.17.177.10])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA20162
          for <questions@freebsd.org>; Tue, 12 Sep 1995 18:11:49 -0700
Received: (from agifford@localhost) by InfoWest.COM (8.6.9/8.6.9) id TAA02403 for questions@freebsd.org; Tue, 12 Sep 1995 19:15:49 -0601
Date: Tue, 12 Sep 1995 19:15:49 -0601
From: Aaron Gifford <agifford@InfoWest.COM>
Message-Id: <199509130116.TAA02403@InfoWest.COM>
To: questions@freebsd.org
Subject: SOMAXCONN question
Sender: questions-owner@freebsd.org
Precedence: bulk

Hi,

I was wondering what would happen if I bumped up the value of SOMAXCONN
from 5 to 15 in <sys/socket.h> and in /usr/src/sys/sys/socket.h and then
recompiled my kernel...  Would it break something?  Also, would it fix
a problem I've noticed on my web server...  when someone begins to connect
over a SLOW or bad link, sometimes `netstat -an | grep SYN_RCVD` shows
that person's multiple connections remaining in the SYN_RCVD state for
quite a while, which appears to make it impossible for anyone else to
connect to the web server until some slots clear.  Not being much of
a socket hacker and not knowing the kernel, I assumed that the listen(sock,max)
queue was full, and that SOMAXCONN was a limiting factor.

Thanks for any and all input,
Aaron Gifford
New to FreeBSD
<agifford@infowest.com>