Re: unbound(8) generating too many log messages

2016-01-15 Thread Philippe Meunier
Raf Czlonka wrote: >How about simply disabling unbound at boot: [...] >and then have something like this in your /etc/hostname.if: Yes, I ended up disabling ntpd and un-enabling unbound in /etc/rc.conf.local and then using: /etc/rc.d/unbound -f start && /etc/rc.d/ntpd -f start at the end of the

Re: unbound(8) generating too many log messages

2016-01-14 Thread Stuart Henderson
Setting 'verbosity: 0' in config will do it, but I don't think it should be necessary. At the very least putting the 'remote address' on the same line as the sendto notice would give syslog something of a chance to reduce the number of lines. Could you ask for suggestions on unbound-users please?

Re: unbound(8) generating too many log messages

2016-01-14 Thread Mike
On 1/14/2016 2:26 AM, Philippe Meunier wrote: >[snip] > The problem is that unbound(8) generates such a pair of messages up to > 20 times for each root server! That's 2 lines * 20 times * 13 root > servers = 520 lines that end up going to syslog. Then 15 seconds > later ntpd(8) tries again and yo

Re: unbound(8) generating too many log messages

2016-01-14 Thread Raf Czlonka
On Thu, Jan 14, 2016 at 07:26:32AM GMT, Philippe Meunier wrote: > Hello, > > I have a laptop computer configured to use unbound(8) and ntpd(8) but > which does not have any network interface configured by default > (except lo0, obviously) since which interface needs to be configured > and how depe

unbound(8) generating too many log messages

2016-01-13 Thread Philippe Meunier
Hello, I have a laptop computer configured to use unbound(8) and ntpd(8) but which does not have any network interface configured by default (except lo0, obviously) since which interface needs to be configured and how depends on where I'm using the computer. After booting, unbound(8) and ntpd(8)