From owner-freebsd-questions Fri Apr 3 14:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14780 for freebsd-questions-outgoing; Fri, 3 Apr 1998 14:13:39 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mail.sodre.net (root@mail.sodre.net [205.152.245.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14731 for ; Fri, 3 Apr 1998 14:12:50 -0800 (PST) (envelope-from cmwagner@tsunami.sodre.net) Received: from tsunami.sodre.net (cmwagner@tsunami.sodre.net [205.152.245.21]) by mail.sodre.net (8.8.8/8.8.8) with ESMTP id RAA02236 for ; Fri, 3 Apr 1998 17:12:39 -0500 Received: (from cmwagner@localhost) by tsunami.sodre.net (8.8.8/8.8.8) id RAA22974 for freebsd-questions@freebsd.org; Fri, 3 Apr 1998 17:12:39 -0500 From: Chad Wagner Message-Id: <199804032212.RAA22974@tsunami.sodre.net> Subject: Building a web server... To: freebsd-questions@FreeBSD.ORG Date: Fri, 3 Apr 1998 17:12:38 -0500 (EST) Content-Type: text 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. Any ideas on building a web server that can handle a significant amount of hits per second would be greatly appreciated. TIA -- -- Chad Wagner cmwagner@fountainauto.com CW1478 -- cmwagner@spaz.org cmwagner@sodre.net cmwagner@oaktree.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message