From owner-freebsd-isp Thu Apr 25 20:19:39 2002 Delivered-To: freebsd-isp@freebsd.org Received: from figg.isecure.com.au (ns2.isecure.com.au [202.125.4.72]) by hub.freebsd.org (Postfix) with ESMTP id 8B03B37B400 for ; Thu, 25 Apr 2002 20:19:29 -0700 (PDT) Received: from iron.isentry.net.au (iron.isecure.com.au [202.125.4.94] (may be forged)) by figg.isecure.com.au (8.11.3/8.11.3) with ESMTP id g3Q3JSL26996 for ; Fri, 26 Apr 2002 13:19:28 +1000 Received: (from smap@localhost) by iron.isentry.net.au (8.11.2/8.10.2) id g3Q3JRA21041 for ; Fri, 26 Apr 2002 13:19:27 +1000 (EST) X-Authentication-Warning: iron.isentry.net.au: smap set sender to using -f Received: from nodnsquery(10.11.3.10) by iron via smap (V5.5) id xma021032; Fri, 26 Apr 02 13:19:18 +1000 Received: from vmail.aipo.gov.au (localhost [127.0.0.1]) by gibbons.isecure.com.au (8.11.3/8.10.2) with ESMTP id g3Q3JIW23227 for ; Fri, 26 Apr 2002 13:19:18 +1000 Received: from pc09011.aipo.gov.au (PC09011.aipo.gov.au [10.0.3.110]) by vmail.aipo.gov.au (8.11.6/8.11.6) with ESMTP id g3Q3JIi31569 for ; Fri, 26 Apr 2002 13:19:18 +1000 (EST) (envelope-from Stanley.Hopcroft@IPAustralia.gov.au) Received: (from anwsmh@localhost) by pc09011.aipo.gov.au (8.11.6/8.11.6) id g3Q3JH409988 for FreeBSD-ISP@FreeBSD.ORG; Fri, 26 Apr 2002 13:19:17 +1000 (EST) (envelope-from anwsmh) Date: Fri, 26 Apr 2002 13:19:17 +1000 From: Stanley Hopcroft To: FreeBSD-ISP@FreeBSD.ORG Subject: Lame DNS question (can't set maxfiles to default after upgrade to Bind 8.2.4/FreeBSD 4.5-RELEASE-p3) Message-ID: <20020426131917.C9401@IPAustralia.Gov.AU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 Dear Ladies and Gentlemen, I am writing to ask your help with a DNS problem. I am writing here rather than questions because this list has shown a lot of interest and help for DNS operational problems like this. After an upgrade from an old 4.3-STABLE to 4.5-RELEASE-p3, bind can no longer set the number of open files to the system limit. Instead on the problem boxes, I see the following after restarting bind. 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. 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 ) bind:\ :tc=default: without any success. BIND is running in a sandbox (started with named -u bind -g bind) Do I need to explicity add the bind class to the password file ? Your advice is very welcome. Thank you, Yours sincerely. -- ------------------------------------------------------------------------ Stanley Hopcroft Network Specialist ------------------------------------------------------------------------ '...No man is an island, entire of itself; every man is a piece of the continent, a part of the main. If a clod be washed away by the sea, Europe is the less, as well as if a promontory were, as well as if a manor of thy friend's or of thine own were. Any man's death diminishes me, because I am involved in mankind; and therefore never send to know for whom the bell tolls; it tolls for thee...' from Meditation 17, J Donne. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message