From owner-freebsd-stable@FreeBSD.ORG Tue Mar 17 19:30:34 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C88301065673 for ; Tue, 17 Mar 2009 19:30:34 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.freebsd.org (Postfix) with ESMTP id 532718FC16 for ; Tue, 17 Mar 2009 19:30:34 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: (qmail 6042 invoked by uid 0); 17 Mar 2009 19:03:53 -0000 Received: from unknown (HELO Grumpy.DynDNS.org) (75.76.211.79) by smtp1.knology.net with SMTP; 17 Mar 2009 19:03:53 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id 09DCE28425; Tue, 17 Mar 2009 14:03:53 -0500 (CDT) Date: Tue, 17 Mar 2009 14:03:53 -0500 From: David Kelly To: Squirrel Message-ID: <20090317190352.GA38038@Grumpy.DynDNS.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable Subject: Re: general: warning: max open files (3636) is smaller than max sockets (4096) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2009 19:30:35 -0000 On Tue, Mar 17, 2009 at 12:31:43PM -0600, Squirrel wrote: > This happend since I've upgraded bind 9.21 to 9.6.0. I've increased > the max open files to 4096: > > sysctl -w kern.maxfiles=4096 > > which shows it resized from 4040->4096 > > But I guess it's different for bind? I've googled and found several > references to this warning message, but everyone states it's not a > problem and shouldn't be concerned. Some real advice would be > appreciated. Depends a lot as to how busy your name server is, I guess. Mine is a lightly loaded in internal office use. When my PII 450 MHz 192MB machine issued similar complaint on upgrade of bind I was tricked into rebooting a machine with over 800 days uptime only to get the exact same message again. So I limited the number of sockets named would ask for using this in /etc/rc.conf: named_flags="-4 -S 1024" -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.