In <list-10080011@2rosenthals.com>, on 06/28/24
at 10:16 AM, "Massimo S." <ecs-isp@2rosenthals.com> said:
Hi Massimo,
>i add, this build start at 92-100% cpu and it's completely unresponsive
>can't be killed and nslookup don't work
>it don't answer to any request, neither in the first seconds after the
>start
Too bad. I suspect the timeout call that Paul implemented is not quite
correct. My thinking was that a 10 second timeout would be a good trade
off between responsiveness and the ability to kill named.
I'd have to see a copy of Paul's patch to have a useful comments on what
Paul implmented.