bind 8.2.3: can't stop greedy cache

Kevin Darcy kcd at daimlerchrysler.com
Wed Feb 7 22:17:31 UTC 2001


It's a well-known fact that BIND 8 just crashes and burns when it runs
into a memory limit, but I thought BIND 9 was supposed to deal more
elegantly. Maybe that part of BIND 9 is still unfinished (????).


- Kevin

Dickmost Saft User Thomas Hoehn wrote:

> We have a bind version 8.2.3 running on our servers
> which handles quite a lot of requests so the named
> cache/process is growing qickly. Trying limit the
> datasize via options didn't work. After I looked into
> source it turned out that this option is not parsed at
> all (src/bin/named/ns_parser.c) and when I tried to
> hardcode the datasize limit for setrlimit in
> src/bin/named/ns_config.c: set_options:
>
> ns_rlimit(Datasize, (u_long) 8388608 /* op->data_size */ );
>
> the limit was ignored. After all I tinkered with a small
> c-programm and found that setting the resource
> RLIMIT_AS (virtual memory limit) for setrlimit
> does the trick. But applied to named the server
> process exits griping in the log with:
>
> xxx default: critical: savedata: memget
>
> So the named can't manage to limit the amount of
> memory it uses? BTW. So does 9.1.0
> Thats pretty bad. Any suggestion?
>
> Thanx in advance,
> Thomas





More information about the bind-users mailing list