Subject: Re: Replacement for grep(1) (part 2)
To: None <email@example.com>
From: Matthew Dillon <firstname.lastname@example.org>
Date: 07/14/1999 15:16:15
:> 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
: 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, email@example.com
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.