Jonathan Marshall - Solaris Software
Sent: Friday, June 18, 2010 3:30 AM
To: Prabhat Rana; bind-users@lists.isc.org; k...@chrysler.com
Subject: Re: out of memory Errors
>
> Yes mine is also 32 bit. So is it confirmed that the 4GB memory limit
on 32 bit processes on Solaris 10?
>
> Prabhat.
&
Yes mine is also 32 bit. So is it confirmed that the 4GB memory limit on 32 bit
processes on Solaris 10?
Prabhat.
Yes, a 32bit process can only access up-to 4gb of memory.
$ echo 2^32 / 1024 / 1024 / 1024 | bc -l
4.
I believe BIND has some options (named.conf) to
On 06/17/10 16:50, Prabhat Rana wrote:
I'm running BIND 9.6.1-P1 in a Solaris 10 server. There is a total of 32G of physical
memory and at any given time about 20G is free. However, named keeps on throwing
"out of memory" errors. When these error occurs in syslog, although
On 6/17/2010 11:50 AM, Prabhat Rana wrote:
I'm running BIND 9.6.1-P1 in a Solaris 10 server. There is a total of 32G of physical
memory and at any given time about 20G is free. However, named keeps on throwing
"out of memory" errors. When these error occurs in syslog, although
I'm running BIND 9.6.1-P1 in a Solaris 10 server. There is a total of 32G of
physical memory and at any given time about 20G is free. However, named keeps
on throwing "out of memory" errors. When these error occurs in syslog, although
named is still running it goes in a hung s
might want to check if you're limiting cache size via
max-cache-size.
- Kevin
raghvendra1.si...@airtel.in wrote:
Hi
We are getting *"could not mark server as lame: out of memory" Errors
*Intermetemtly in DNS bind version BIND
Hi
We are getting "could not mark server as lame: out of memory" Errors
Intermetemtly in DNS bind version BIND 9.4.3 on Solaris
08-May-2009 11:52:57.090 resolver: could not mark server as lame: out of
memory
08-May-2009 11:53:07.204 resolver: could not mark server as lame: out
7 matches
Mail list logo
