On 9/10/2013 at 10:02 AM W.C.A. Wijngaards wrote: |-----BEGIN PGP SIGNED MESSAGE----- |Hash: SHA1 | |Hi Mike, | |On 09/04/2013 03:26 AM, Mike. wrote: |> |> |> On 9/3/2013 at 9:12 PM zongo saiba wrote: |> |> |Greetings to all, | |platform: OSX 10.8.4 | |I have been trying |> unbound for about 1 month now and it is a fantastic |piece of |> software. |I have one issue (not really one), but my logs are |> filling up with: | |03/09/2013 21:07:08.707 unbound: *** |> process 128 exceeded 500 log |message per second limit - |> remaining messages this second discarded *** |03/09/2013 |> 21:07:10.387 unbound: *** process 128 exceeded 500 log |> |message per second limit - remaining messages this second |> discarded *** | |I was wondering if anyone has had the issue before |> on OSX and how to |stop the log pollution if at all possible ? |> ============= |> |> I have seen a problem with excessive logging previously on |> FreeBSD. |> |> I was seeing 20 log records per millisecond (20,000 log records |> per second) and continuing for a couple of seconds. Log verbosity |> was set to 1. |> |> Here is the thread: |> http://unbound.net/pipermail/unbound-users/2013-June/002941.html | |In recent unbound versions this should be fixed after you reported it, |(it should not log them at verbosity 1, but will show you this |'spammy' issue at higher log levels). | ============= Thanks for the reply (and the fix!). I'll do an install from source to resolve the issue on my end. Thanks again! Mike.