From owner-freebsd-questions Thu Apr 12 16: 8:43 2001 Delivered-To: freebsd-questions@freebsd.org Received: from luke.cpl.net (luke.cpl.net [63.169.72.3]) by hub.freebsd.org (Postfix) with ESMTP id 698B137B423 for ; Thu, 12 Apr 2001 16:08:41 -0700 (PDT) (envelope-from shawn@cpl.net) Received: from shawn (shawn.cpl.net [63.169.72.21]) by luke.cpl.net (8.9.3/8.9.3) with SMTP id QAA06187 for ; Thu, 12 Apr 2001 16:08:35 -0700 (PDT) Message-ID: <005001c0c3a5$32d342a0$1548a93f@cpl.net> From: "Shawn Ramsey" To: Subject: fdlimit? Date: Thu, 12 Apr 2001 16:06:24 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apr 12 15:57:07 named[9367]: limit files set to fdlimit (1024) I am getting that when named starts up... and named is dying very frequently. Maybe every few days. I would guess the two are related, but I don't see why I am getting that error. Maxfiles is set to a high level (too high?), and the server is not under any load. Its just doing FR(128k) routing for a small lan, nat, and DNS. # sysctl kern.maxfiles kern.maxfiles: 8232 There are no other error messages being logged, and no other problems... system seeems to run ok other than this. The server is running FreeBSD 4.2-RELEASE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message