From owner-freebsd-questions Fri Apr 3 14:49:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21545 for freebsd-questions-outgoing; Fri, 3 Apr 1998 14:49:27 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21451 for ; Fri, 3 Apr 1998 14:48:06 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id OAA07396; Fri, 3 Apr 1998 14:47:11 -0800 (PST) Message-Id: <199804032247.OAA07396@implode.root.com> To: Chad Wagner cc: freebsd-questions@FreeBSD.ORG Subject: Re: Building a web server... In-reply-to: Your message of "Fri, 03 Apr 1998 17:12:38 EST." <199804032212.RAA22974@tsunami.sodre.net> From: David Greenman Reply-To: dg@root.com Date: Fri, 03 Apr 1998 14:47:11 -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I am working on building a web server that runs under FreeBSD 2.2.6, and I was >wondering what can be done in the case of 'port clogging', i.e. too many >requests to the port and it is backlogged due to this. What can be done to >alleviate this? It seems like a TCP implementation issue, but almost every >UNIX OS does it this way, obviously for a reason which is unknown to me. The usual solution to this is to increase the listen queue depth. There is a kernel limit (kern.somaxconn or kern.ipc.somaxconn depending on which version of FreeBSD), and of course the value passed into listen() needs to also be increased. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message