> 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, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Replacement for grep(1... Matthew Dillon
- Re: Replacement for grep(1... Nate Williams
- Re: Replacement for grep(1... Matthew Dillon
- Re: Replacement for grep(1... Nate Williams
- Re: Replacement for grep(1) (p... Ville-Pertti Keinonen
- Re: Replacement for grep(1) (part 2) Daniel C. Sobral
- Re: Replacement for grep(1) (part 2) Robert Elz
- Re: Replacement for grep(1) (part 2) Daniel C. Sobral
- Re: Replacement for grep(1) (part 2... Robert Elz
- Re: Replacement for grep(1) (p... Matthew Dillon
- Re: Replacement for grep(1... sthaug
- Re: Replacement for grep(1... Matthew Dillon
- Re: Replacement for grep(1) (p... Daniel C. Sobral
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Noriyuki Soda
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Noriyuki Soda
- Re: Replacement for grep(1) (part 2... Matthew Dillon
- Re: Replacement for grep(1) (p... Noriyuki Soda
- Re: Replacement for grep(1... Matthew Dillon
- Re: Replacement for grep(1... Ted Faber