From owner-freebsd-questions  Wed Jan 15 09:03:38 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id JAA11175
          for questions-outgoing; Wed, 15 Jan 1997 09:03:38 -0800 (PST)
Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA11135
          for <freebsd-questions@FreeBSD.ORG>; Wed, 15 Jan 1997 09:03:19 -0800 (PST)
Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.3/8.8.3) with SMTP id MAA02699; Wed, 15 Jan 1997 12:04:07 -0500 (EST)
Message-Id: <3.0.32.19970115115400.009585b0@sentex.net>
X-Sender: mdtancsa@sentex.net
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Wed, 15 Jan 1997 11:54:01 -0500
To: neil@corpex.com (Neil), freebsd-questions@FreeBSD.ORG (Questions Freebsd)
From: Mike Tancsa <mike@sentex.net>
Subject: Re: Named open files
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

At 04:26 PM 1/15/97 +0000, Neil wrote:
>Hi,
>	We are running  named 4.9.4-P1 under freebsd 2.1.0 on a P166,
>The kernel has been recompiled with the following options
>
>maxusers 64
>options	"CHILD_MAX=128"
>options	"OPEN_MAX=360"
>
>	It also got approx 300 IP numbers ifconfig'd as aliases to the
>ep0 ethernet port.
>
>	Now sometimes when named is rebooted, we get the following error.
>
>named[6931]: socket(SOCK_DGRAM): Too many open files - exiting
>
>	I assume this has to do with ifconfig and named trying to bind to
>too many IP numbers. Now is there a patch for named that we can use?


In your named.restart, add something like

ulimit -n 1000

This will allow the process to have as many as 1000 files open...

	---Mike