| raw e-mail | index | archive | help
Here is the warning on a fresh VM with 8GB:
# sysctl hw.physmem
hw.physmem: 8551202816
# service local_unbound onestart
Starting local_unbound.
[1759883902] local-unbound[3237:0] warning: setsockopt(...,
SO_SNDBUF, ...) was not granted: No buffer space available
[1759883902] local-unbound[3237:0] warning: so-sndbuf 4194304 was
not granted. Got 9216. To fix: start with root permissions(linux) or
sysctl bigger net.core.wmem_max(linux) or kern.ipc.maxsockbuf(bsd)
values. or set so-sndbuf: 0 (use system value).
[1759883902] local-unbound[3237:0] warning: setsockopt(...,
SO_SNDBUF, ...) was not granted: No buffer space available
[1759883902] local-unbound[3237:0] warning: so-sndbuf 4194304 was
not granted. Got 9216. To fix: start with root permissions(linux) or
sysctl bigger net.core.wmem_max(linux) or kern.ipc.maxsockbuf(bsd)
values. or set so-sndbuf: 0 (use system value).
Waiting for nameserver to start... good
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.
Regards,
>
> --
> 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=3D0
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>