From owner-freebsd-stable Mon Mar 9 11:21:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10154 for freebsd-stable-outgoing; Mon, 9 Mar 1998 11:21:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ziplink.net (relay-0.ziplink.net [206.15.168.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10005 for ; Mon, 9 Mar 1998 11:20:29 -0800 (PST) (envelope-from lrios@ziplink.net) Received: from zip1.ziplink.net (zip1.ziplink.net [206.15.168.18]) by ziplink.net (8.8.7/8.8.7) with SMTP id NAA12381 for ; Mon, 9 Mar 1998 13:54:08 -0500 (EST) Date: Mon, 9 Mar 1998 13:57:02 -0500 (EST) From: lrios To: freebsd-stable@FreeBSD.ORG Subject: Named and BSD 2-2-5 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I'm running Bind 8.1.1 on a pentinum II 266 with 128M of memory and approx. once every two to three days named dumps core claiming calloc errors (see below) 1) Has anyone experienced this problem with a similar setup?? 2) What can I do to stop this error?? I have inserted some extra options in the kernel as maxchild but other than that it's pretty stock.. Heres a copy of this error: 11:29:44 picnic Mar 9 11:29:44named[: qnew: calloc failed Mar 9 11:29:44 picnic Mar 9 11:29:44named[: qnew: calloc failed Mar 9 11:29:44 picnic Mar 9 11:29:44named[: qnew: calloc failed Mar 9 11:29:49 picnic /kernel: pid 1186 (named), uid 0: exited on signal 6 (cor e dumped) Any help would be very helpful.. ______ __ /___ / / / __ / /(@)__ / (@)__ / /__ lrios@ziplink.net / // / _ \/ / / _ \/ '_/ / //_/ .__/_/_/_//_/_/\_\ NASA TEAM / /__/_/___________________ `He who dies with the most toys win!` /___________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message