From owner-freebsd-isp Thu Apr 25 20:58:30 2002 Delivered-To: freebsd-isp@freebsd.org Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by hub.freebsd.org (Postfix) with ESMTP id E324537B404 for ; Thu, 25 Apr 2002 20:58:25 -0700 (PDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 170w33-0002TZ-00; Thu, 25 Apr 2002 20:05:25 -0700 Date: Thu, 25 Apr 2002 20:05:13 -0700 (PDT) From: Tom Samplonius To: Stanley Hopcroft Cc: FreeBSD-ISP@FreeBSD.ORG Subject: Re: Lame DNS question (can't set maxfiles to default after upgrade to Bind 8.2.4/FreeBSD 4.5-RELEASE-p3) In-Reply-To: <20020426131917.C9401@IPAustralia.Gov.AU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 26 Apr 2002, Stanley Hopcroft wrote: ... > Apr 26 12:38:00 wins named[22746]: reloading nameserver > Apr 26 12:38:00 wins named[22746]: setrlimit(max number of open files): > Operation not permitted > Apr 26 12:38:00 wins named[22746]: Ready to answer queries. Only root can use setrlimit() to raise the maximum (hard) limit. Do you know how high named is trying to set the limit? > On other words, it seems highly unlikely that replication will work. > > I have added an entry for BIND to login.conf and remade the > login database (with cap_mkdb /etc/login.conf ) ... Quite likely this all you need to do. named will not have to setrlimit() to a higher limit, if the existing limit is ok, right? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message