Re: Running out of buffers?

[Roy Marples <roy%marples.name@localhost>]

On 27/04/2018 23:58, Robert Elz wrote:
>      Date:        Fri, 27 Apr 2018 21:34:49 +0100
>      From:        Roy Marples <roy%marples.name@localhost>
>      Message-ID:  <df3a6231-f417-1d79-f135-bef0fe2f5a45%marples.name@localhost>
>
>    | Hopefully this fixes the issues and won't impact small memory devices
>    | too much.
>
> While those are probably useful changes to make, they don't fix anything,
> merely make it less likely.

Until we can dynamically size the buffer in the kernel on demand you are 
correct.

> We really need to turn off the error on recv() by default - and allow it
> to be turned on by applications that actually want to deal with this.

Why should we special case reporting this error instead of others?
While NetBSD might be the first BSD to report ENOBUFS for recv(), it's 
certainly not the first OS to do so.

Looking at Pauls logs, ntpd is reporting this a fair bit.
Looking at ntpd, it already *has* logic to deal exclusivly with this 
error - it logs it and continues. Any other error and it closes the 
socket and gives up.

Roy