| raw e-mail | index | archive | help
Thinking out loud:
Without more context in the upstream commit log message it's difficult we
must surmise that the wait for ARP/NDP resolution could be due to a very
busy unbound service combined with latency in ARP/NDP resolution. I haven't
found any upstream Github issues that document this problem.
Maybe there's a pattern waiting to be discovered. Let's open a PR for this
to gather more information. I'd also be inclined to open an upstream Github
issue for this problem.
Questions I have are:
1. What is similar about the systems with this problem?
2. What was upstream *really* trying to solve? Was it a Linux-only problem
or
more, i.e. affecting FreeBSD also?
There is no default configuration file shipped with FreeBSD. Though we
should probably include one. That would be the simplest, least intrusive
mitigation of upstream's mitigation.
As my machine here that does use local_unbound has had no such warnings I'm
unable to reproduce the problem locally.
--
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org
NTP: <cy@nwtime.org> Web: https://nwtime.org
e**(i*pi)+1=0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>