From owner-freebsd-isp Tue Feb 11 10:54:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA10556 for isp-outgoing; Tue, 11 Feb 1997 10:54:13 -0800 (PST) Received: from buffnet4.buffnet.net (root@buffnet4.buffnet.net [205.246.19.13]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA10549 for ; Tue, 11 Feb 1997 10:54:02 -0800 (PST) Received: from buffnet1.buffnet.net (mmdf@buffnet1.buffnet.net [205.246.19.10]) by buffnet4.buffnet.net (8.6.12/8.6.9) with SMTP id NAA24302 for ; Tue, 11 Feb 1997 13:54:37 -0500 Received: from buffnet11.buffnet.net by buffnet1.buffnet.net id aa12853; 11 Feb 97 13:53 EST Date: Tue, 11 Feb 1997 13:53:37 -0500 (EST) From: Steve To: Jason Fesler cc: Dan Busarow , Chris Bura , freebsd-isp@freebsd.org Subject: Re: Apache In-Reply-To: <3.0.32.19970211083120.009b2c70@pop.calweb.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 11 Feb 1997, Jason Fesler wrote: > At 11:33 AM 2/10/97 -0800, Dan Busarow wrote: > >> Does it have to do with the number of V hosts? Is 125 really high? > > > >It might. If you're running named on this machine it may be having > >problems caused by binding to all the addresses. If you are running > >named on this machine try turning it off and pointing to another > >nameserver in /etc/resolv.conf > > We have *definately* seen this behavior; I've also read about this in > an FAQ somewhere (where, I don't remember... the grey matter upstairs > went on strike). We *tried* to run DNS on such a server (400 hosts), > and it kept dying, not starting, etc *after* the IP aliases were defined. > It would do fine if we started *before*. We ended up moving the DNS > server to a different machine (it was only a secondary) instead of > reading the source code due to time constraints. I had this happen - but I just upped some of the kernal config items - like max users, max opens, max procs, recompiled and it went away.