netstat showing multiple lines for each listening socket

Hello, we have been running some BIND nameservers on Debian-based systems for many years. Until (including) Debian 10 with BIND 9.11.5, netstat always showed only one line per listening socket, e.g. tcp0 0 10.x.x.x:53 0.0.0.0:* LISTEN 1234/named tc

Re: netstat showing multiple lines for each listening socket

s. Robert Wagner From: bind-users on behalf of Thomas Hungenberg via bind-users Sent: Monday, July 8, 2024 4:52 AM To: bind-users@lists.isc.org Subject: netstat showing multiple lines for each listening socket This email originated from outside of TESLA Do not c

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

On 10.07.24 14:20, Tom Marcoen (EXT) wrote: My server has four (virtual; it runs on vSphere) CPUs and also shows four lines in `ss` output. The `ps` command shows the `-U` which - I assume - is set automatically triggered by the number of CPUs. # ps -elf | grep named 5 S named23769 1