On Tue, Oct 07, 2025 at 09:44:42PM -0300, Jose Luis Duran wrote: J> Here is the warning on a fresh VM with 8GB: J> J> # sysctl hw.physmem J> hw.physmem: 8551202816 J> # service local_unbound onestart J> Starting local_unbound. J> [1759883902] local-unbound[3237:0] warning: setsockopt(..., J> SO_SNDBUF, ...) was not granted: No buffer space available J> [1759883902] local-unbound[3237:0] warning: so-sndbuf 4194304 was J> not granted. Got 9216. To fix: start with root permissions(linux) or J> sysctl bigger net.core.wmem_max(linux) or kern.ipc.maxsockbuf(bsd) J> values. or set so-sndbuf: 0 (use system value).
Why would local-unbound want such a big send buffer? Doesn't make sense to me. -- Gleb Smirnoff
