Jose Luis Duran wrote in
<CAPwQLcd8cuttgT4tYcExcQraWYisRECfe49_XkCyvrZ3pW=z...@mail.gmail.com>:
> > > > This means so-sndbuf is now 4m. Which triggers a warning, detailed in
> > > > upstream commit 713b5db5 ("- Fix to print warning for when so-sndbuf
> > > > setsockopt is not granted.").> > > > I wonder if we should revert back to using "so-sndbuf: 0" as the > > > > default for FreeBSD? Or is there a better solution/workaround? > If we configure it with "so-sndbuf: 0" the warning goes away. > But, nevermind if I'm the only one seeing these warnings. It was just > a basic local_unbound test. it's not just you, a user on IRC also reported this issue on a system with 256GB memory. i would be inclined to add so-sndbuf: 0 to the default configuration, but i haven't looked at the actual problem here in detail (i don't use local_unbound myself).
signature.asc
Description: PGP signature
