At Tue, 05 Jan 2010 10:36:27 +0200,
Imri Zvik im...@inter.net.il wrote:
i have a high load DNS server running bind 9.4.3 on RH -
yesterday we experienced a problem with the bind (the bind froze) , and
when looking at the logs i saw the following error :
named error: socket: file
On Sunday 03 January 2010 16:36:06 Ram Akuka wrote:
i have a high load DNS server running bind 9.4.3 on RH -
yesterday we experienced a problem with the bind (the bind froze) , and
when looking at the logs i saw the following error :
named error: socket: file descriptor exceeds limit
Shumon Huque wrote:
On Mon, Jan 04, 2010 at 01:43:52PM -0500, Kevin Darcy wrote:
named seems to use, by default, the OS hard limit on file descriptors,
even though the ARM says The default is |unlimited|. . When it starts
up as superuser, in theory it should be able to set both the hard and
What's your hard limit (ulimit -n -H)?
named seems to use, by default, the OS hard limit on file descriptors,
even though the ARM says The default is |unlimited|. . When it starts
up as superuser, in theory it should be able to set both the hard and
soft limit to infinity, but it doesn't
On Mon, Jan 04, 2010 at 01:43:52PM -0500, Kevin Darcy wrote:
named seems to use, by default, the OS hard limit on file descriptors,
even though the ARM says The default is |unlimited|. . When it starts
up as superuser, in theory it should be able to set both the hard and
soft limit to
5 matches
Mail list logo
