unbound generating too many log messages

[W.C.A. Wijngaards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Mike,

On 19/01/16 16:37, Mike via Unbound-users wrote:
> On 1/19/2016 10:20 AM, Taylor R Campbell via Unbound-users wrote:
>> 
>> That's irrelevant to the issue Philippe raised.  The network is
>> not always available, no matter how well you configure your
>> system or engineer your software.  The problem here is that when
>> the network is down, Unbound spews junk to its log as fast as it
>> can.
>> 
>> [snip]
> 
> At one point, on this mailing list I documented 20,000 syslog
> messages per second from unbound when the network interface was
> unavailable for a couple of seconds. 
> http://marc.info/?l=unbound-users&m=137166462329717&w=2
> 
> While unbound logging has improved a bit since then, I still see
> far too many essentially duplicate syslog messages for a single
> network unavailable event.
> 
> If I need high volume logging for troubleshooting, I'll increase
> the logging verbosity.  Logging should be something that is
> helpful, not something I cringe about.

Is it always the "sendto failed:" error that makes you cringe?  That
aren't already squelched by logging verbosity?  Is there an errno that
I should also squelch, or should I squelch all errors from the
sendto() system call?

Best regards, Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWnlsvAAoJEJ9vHC1+BF+Nu68P/An7ukx6Uuwkx7yRduyChCdt
BSHCCVOYUKhd6CADp8gmkd5IHHeecCB5edMw+/ueUMEmU3vQgFQuAxmHmkXyMrWD
sgaTIKOsFWZCzN8inG8SJlufhEpgOY/MvrubgY7frwz/YWHo7zjl42miGxBm05RT
k85OpPbG9uipYuILImHEO2H+iKyN9SqNioCP4RKyicJoxuNPmwjYVZAXJ16l7Z8p
VxrwKb9KJ46b3EWfpMihpz64UTJbaDBqSWgPE7EzMR4yDHIAIPt7gzWrxO1nozkF
U+FX3jXmp3fn9J+GFpV1hjA/zhHf4a/lEiFABXNZ617Z4rq9W21N2D62aBF34bn+
gK2h9VDPpGpd2scJ3sBX891rrE/HM3kU12pns4BSgFQcyrPzSy/9i+Y+CgqhqSNs
fUiHWImIVfsIW4CamhDpwUC+cL43Zeegv/1A5UttAnwQ+iGpTvyu1N4YGo60MBZt
Mw9faG0QNsCWyZcZki04CfTOAWlL862qwIw4EXpWZb9B8lrl2fEyDDnTm2h90FdI
GBt7iT22bUj8BE2yxKUo5WBzKaZmIlcTgCO3E3hmOwMF07h+9uIOdTSGI2uCSbd/
kwOhNGvUItn0SHi1m12EhRWHYl++YQiqUygnXG3D30l8MgqdnGDPGfez47Ba4aEZ
iqGKlt1T72IKPOsvgEg2
=zO0r
-----END PGP SIGNATURE-----