From owner-freebsd-questions Tue Dec 24 17:00:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA19173 for questions-outgoing; Tue, 24 Dec 1996 17:00:30 -0800 (PST) Received: from gdi.uoregon.edu (cisco-ts9-line15.uoregon.edu [128.223.150.96]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA19156 for ; Tue, 24 Dec 1996 17:00:17 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id RAA00280; Tue, 24 Dec 1996 17:00:03 -0800 (PST) Date: Tue, 24 Dec 1996 17:00:03 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Chris Bura cc: questions@freebsd.org Subject: Re: "Too many open files" Question In-Reply-To: <32C03589.1C05@netcorps.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 24 Dec 1996, Chris Bura wrote: > Problem: When I edit an entry in my DNS and then run Kill -HUP PID > my name server does not restart. This is the message I get > in /var/log/messages: > ------- > Dec 24 11:27:33 main named[68]: reloading nameserver > Dec 24 11:27:33 main named[68]: socket(SOCK_DGRAM): Too many open files > - exiting > ------- > I've tried, named.restart, named.reload, named -b .... > However, if I reboot, the name server reloads just fine. > I've increased the MAX_OPEN significantly. Didn't help. I'm guessing you run many virtual domains. Before reloading named you need to run the following command: limit openfiles=128 or limit openfiles=360 Or ulimit This expands or removes the shell open files limitation. This is somewhat dependent on your shell. There are many instances of this in the mail archvies. Search for 'named AND open', with the same Hope this helps. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major