Thanks for the feedback
> How many sockets are open when you see this message? Normally the
> socket() call shouldn't fail even if named uses many sockets
> (it will fail anyway, but the failure mode is normally
> different), so it's very odd to see the above message.
As Jeremy suggested we
At Thu, 14 May 2009 17:46:42 +0200,
"Philippe Maechler" wrote:
> > > I'm running a bind 9.4.2-p2 and a 9.5.1-P1 both on a
> > FreeBSD 6.x box
> > > as caching servers.
> > > let's call them ns1 and ns2 :P
> > >
> > > short after we shutdown server one we get error messages on
> > the other se
Hello Jeremy
> >
> > I'm running a bind 9.4.2-p2 and a 9.5.1-P1 both on a
> FreeBSD 6.x box
> > as caching servers.
> > let's call them ns1 and ns2 :P
> >
> > short after we shutdown server one we get error messages on
> the other server
> > -> socket: too many open file descriptors
>
> What
On Thu, 14 May 2009, Philippe Maechler wrote:
> Hello Everybody
>
> I'm running a bind 9.4.2-p2 and a 9.5.1-P1 both on a FreeBSD 6.x box as
> caching servers.
> let's call them ns1 and ns2 :P
>
> short after we shutdown server one we get error messages on the other server
> -> socket: too many o
Hello Everybody
I'm running a bind 9.4.2-p2 and a 9.5.1-P1 both on a FreeBSD 6.x box as
caching servers.
let's call them ns1 and ns2 :P
short after we shutdown server one we get error messages on the other server
-> socket: too many open file descriptors
I tried to recompile named with FD_SETSIZ
5 matches
Mail list logo
