From owner-freebsd-isp Wed Jul 23 21:32:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA07102 for isp-outgoing; Wed, 23 Jul 1997 21:32:23 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA07091; Wed, 23 Jul 1997 21:32:15 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id AAA14490; Thu, 24 Jul 1997 00:35:45 -0400 (EDT) Date: Thu, 24 Jul 1997 00:35:45 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Marc Slemko cc: Aaron Jackson , gpalmer@FreeBSD.ORG, nevin@deepwell.com, freebsd-isp@FreeBSD.ORG Subject: Re: Limits on apache In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 23 Jul 1997, Marc Slemko wrote: > With 1.2.0, that won't work a lot of the time because BIND has broken code > that sets a hard limit based on the FD_SETSIZE setting when BIND was > compiled. You would have to recompile the resolver library with a larger > FD_SETSIZE to fix that on 1.2.0. On a tangent... I assume (correct me if I'm wrong...) what you are talking about here is apache doing the reverse lookups for logging. We used to let apache do this until I hit some of our sites from unnamed hosts and saw an incredible slowness in downloading just about anything from our webservers. Ping and traceroute showed excellent connectivity, and I figured out the delay was apache doing the lookups and waiting on the timeout... Turning off dns lookups in the apache configs made things fly, and we now run sans dns lookups and let analog do the lookups when it processes the logs. We've since gotten some positive responses from clients coming in from ISPs that don't do revs on most of their dialup connections. Charles