From owner-freebsd-stable Mon Aug 21 10:40:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id DFC9337B423 for ; Mon, 21 Aug 2000 10:40:54 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7LHepF69416; Mon, 21 Aug 2000 10:40:52 -0700 (PDT) Date: Mon, 21 Aug 2000 10:40:51 -0700 (PDT) From: Doug White To: Jonathan Defries Cc: "Freebsd-Stable@Freebsd. Org" Subject: Re: Too many open files In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Aug 2000, Jonathan Defries wrote: > Hi all, > > I'm trying to run a caching nameserver on one of my web servers > and it keeps complaining: > > socket(SOCK_DGRAM): Too many open files In addition to the login.conf/limits hint, check the sysctl kern.maxfiles and kern.maxfilesperproc > What's the best thing to do to try and alleviate this? I have > maxusers set at 256, I've seen mention of a new kernel with a > couple of extra options, would this be the way to go? Note that bind opens two listening sockets per configured IP address. If you have several aliases on one interface it'll open 2*#IPs and probably hit the limit. You probably want to limit named to binding to specific IPs; see the 'listen-on' option, e.g. options { listen-on { 127.0.0.1; 192.168.1.2; }; }; Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message