Olaf Hoyer wrote:
On Fri, 4 Jun 2004, Rob wrote:
named claims memory on the fly.
On Solaris, I have bind 8 seen claiming about 800MB RAM for its caching
database, being the resolver for the machine that creates from http-logs
colorful pictures and other fancy things...
Waaauw, that sounds rather d
On Fri, 4 Jun 2004, Rob wrote:
> >
> > named claims memory on the fly.
> > On Solaris, I have bind 8 seen claiming about 800MB RAM for its caching
> > database, being the resolver for the machine that creates from http-logs
> > colorful pictures and other fancy things...
>
> Waaauw, that sounds ra
Olaf Hoyer wrote:
On Fri, 4 Jun 2004, Rob wrote:
No change at all in memory usage. If named keeps its cache in memory,
why do I not see any changes of available swap space when starting named?
Or does named claim memory on the fly, as it is caching?
If so, how can I find out what is the maximum it
On Fri, 4 Jun 2004, Rob wrote:
> No change at all in memory usage. If named keeps its cache in memory,
> why do I not see any changes of available swap space when starting named?
>
> Or does named claim memory on the fly, as it is caching?
> If so, how can I find out what is the maximum it can cla
Rob wrote:
Hi,
This is on FreeBSD 4-Stable.
I have set up a caching name server. About its cached data base,
I found out:
1) data base is kept in memory
2) the maximum memory is adjustable in named.conf, for example:
datasize 20M;
But without specifying the datasize, how much memory is
Hi,
This is on FreeBSD 4-Stable.
I have set up a caching name server. About its cached data base,
I found out:
1) data base is kept in memory
2) the maximum memory is adjustable in named.conf, for example:
datasize 20M;
But without specifying the datasize, how much memory is used by
def
