-------- Original Message -------- On Sunday, 12/21/25 at 20:34 Stuart Henderson <[email protected]> wrote:
> How is OpenBSD responsible for *a file which you have added yourself*?! Because I did not add them myself. I found them there, written by base. > On logs, you are jumping to conclusions. My real configuration is not the one > I posted here for the sake of testing. > So you have a problem with resolution failures but you report a problem with > reloading not working. No, I wrote about daemon reloading failure. > so-sndbuf is relating to a kernel limit not something inside unbound. > it does different things on linux (socket buffer) compared to BSDs (just > limiting the size of a single packet). > they bumped it to work around a problem some people were seeing *on linux* > (filling the buffer which OpenBSD dodsn't have when waiting for ARP > responses), they changed from a value which is overkill for what that setting > does on BSDs (but was accepted anyway) to a value which is not accepted at all. > their advice to recompile kernels on OpenBSD is poor. I am neither in their shoes nor in yours. What I see in the debug log is a warning that a critical resource is not avilable. Jumping to the conclusion that the warning is mistaken is something that I cannot do. You can, I cannot. What I can do is to question whomever ported unbound to openbsd and did not solve the problem. If it is true that so-sndbuf means different things in linux and openbsd, then the warning needed to be removed or corrected. Since the warning is there, then the problem holds, and whomever bumps into it, as I did here, feels the need to solve it. > I give up trying to help. You did what you could do. Thank you.
