Re: syslog, ENOBUFS and non-C implementations

[Lloyd Parkes <lloyd%must-have-coffee.gen.nz@localhost>]

Kia ora koutou katoa,

On Tue, 2024-03-05 at 11:19 +0100, Havard Eidnes wrote:
> 
> Secondly: is it something particular we are doing on the NetBSD
> end of things which contributes to this problem?  Doesn't other
> OSes return ENOBUFS if syslogd isn't able to keep up by consuming
> the messages at the receiving end?

It seems that other OSes do not return ENOBUFS. The following is from a
Debian manual page for send(2).

> ENOBUFS
>        The  output queue for a network interface was full.  This
> gener‐
>        ally indicates that the interface has stopped sending,  but 
> may
>        be caused by transient congestion.  (Normally, this does not
> oc‐
>        cur in Linux.  Packets are just silently dropped when  a 
> device
>        queue overflows.)

This doesn't seem like the most useful behaviour to me, but it will
explain what you are seeing.

Ngā mihi,
Lloyd