From owner-freebsd-hackers Wed Jul 14 15:16:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E5C27153C5 for ; Wed, 14 Jul 1999 15:16:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA96558; Wed, 14 Jul 1999 15:16:15 -0700 (PDT) (envelope-from dillon) Date: Wed, 14 Jul 1999 15:16:15 -0700 (PDT) From: Matthew Dillon Message-Id: <199907142216.PAA96558@apollo.backplane.com> To: sthaug@nethelp.no Cc: kre@munnari.OZ.AU, freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org Subject: Re: Replacement for grep(1) (part 2) References: <199907142105.OAA96038@apollo.backplane.com> <1955.931987797@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> Also, your named is badly misconfigured if it grows to 130MB. We never :> allow ours to grow past 30MB. : :How do you know what kind of name server configuration kre is running? :Here's an example of a name server running *non-recursive*, serving :11.500 zones: : : PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND :27162 root 2 0 70M 57M sleep 271:01 3.27% 3.27% named : :Are you saying that such configurations should be illegal? : :Steinar Haug, Nethelp consulting, sthaug@nethelp.no I assumed that since the guy said that his named GREW, that he was running a recurisve/caching named. Obviously if you are running a non-recursive named the static size will depend on the zones you are serving. Duh! It is not generally beneficial to allow a caching named to exceed 30MB or so on a system that is doing other things. If the system starts to page (which this person's system is obviously doing), then it is doubly a bad idea to allow a named to grow that large. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message