Re: netstat showing multiple lines for each listening socket

I’m afraid we’re a little out of sync between the documentation and the code, depending on which code you’re running. -U was changed some time ago to mean the number of dispatchers to use for outgoing queries, not listeners to use for incoming queries. Post 9.18 it won’t do anything at all, so

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

RE: netstat showing multiple lines for each listening socket

users@lists.isc.org Onderwerp: 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

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

> -Original Message- > From: bind-users On Behalf Of Thomas > Hungenberg via bind-users > Sent: Monday, 8 July 2024 10:53 > To: bind-users@lists.isc.org > Subject: netstat showing multiple lines for each listening socket > > Hello, > > we have been running s

Re: netstat showing multiple lines for each listening socket

, you may be able to track back to the root > > process and determine if these are just service threads. > > > > > > Robert Wagner > > > > > > From: bind-users on behalf of Thomas > > Hungenberg via bind-users >

RE: netstat showing multiple lines for each listening socket

127.0.0.1:953 *:* users:(("named",pid=9623,fd=62)) -Oorspronkelijk bericht- Van: bind-users Namens Thomas Hungenberg via bind-users Verzonden: maandag 8 juli 2024 13:13 Aan: Robert Wagner ; bind-users@lists.isc.org Onderwerp: Re: netstat showing multiple lines for eac

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

That's correct. Since BIND 9.16, `named` binds to individual addresses instead of "any" because it needs to send responses back from the same address and it's just easier this way. Cheers, -- Ondřej Surý (He/Him) ond...@isc.org My working hours and your working hours may be different. Please do

Re: netstat showing multiple lines for each listening socket

-users@lists.isc.org Subject: netstat showing multiple lines for each listening socket This email originated from outside of TESLA Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello, we have been running some BIND nameservers on Debian

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