Re: netstat showing multiple lines for each listening socket

On 08.07.24 15:59, Lee wrote: How many cpus does your machine have? I'm running bind at home; not a whole lot of traffic to named so it seemed like all those threads were a waste. So pretend there's only one cpu: $ grep bind /etc/default/named # OPTIONS="-u bind " OPTIONS="-u bind -n 1" Tha

RE: netstat showing multiple lines for each listening socket

el9 bind-9.16, maybe netstat/os? tcp0 0 x.x.x.x:530.0.0.0:* LISTEN 46622/named tcp0 0 y.y.y.y:530.0.0.0:* LISTEN 46622/named tcp0 0 127.0.0.1:53 0.0.0.0:* LISTEN 46622/named >

Re: zone_journal_compact: could not get zone size: not found

You need to ask your supplier. BIND 9.16 is end-of-life and for all practical purposes, everything that ISC provides doesn't have the problem. Unfortunately, RedHat decided to provide FreeIP dyndb plugin under incompatible license with BIND 9, so we can't really do anything about that. Ondrej -

Re: zone_journal_compact: could not get zone size: not found

Indeed the LDAP plugin does not provide the getsize method. Until now it never has. I'll notify the maintainer. I have a question that you may be able to answer. Is the getsize method a required method or an optional one? If the latter then the zone_journal_compact function needs to become a b