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
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
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
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
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
>
-users
> Verzonden: maandag 8 juli 2024 13:13
> Aan: Robert Wagner ; bind-users@lists.isc.org
> Onderwerp: Re: netstat showing multiple lines for each listening socket
>
> Hi Robert,
>
> it's the same PID for all lines, parent process is systemd.
>
> The lines in
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
Hi Robert,
it's the same PID for all lines, parent process is systemd.
The lines in the netstat output are exact duplicates (same IP, port and PID).
Other tools like ss show the same, so it's not a problem with netstat.
It's the same bahaviour on different machines, some upgraded from Debian <
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
Some diagnostics is needed. When you reboot, does it show it up multiple binds
to the same port? Can your run netstat -tP to identify the process ID (are
they the same or different). There may also be other options to provide more
diagnostics.
-Trying to determine if you are really binding
10 matches
Mail list logo