From 124f3ecad938ec0a544f2b23b57a966895efa75f Mon Sep 17 00:00:00 2001
From: Joris Vink <joris@coders.se>
Date: Wed, 26 Jun 2013 15:59:42 +0200
Subject: [PATCH] no need to use kore_log() in a debug context

---
 modules/example/module.conf | 2 +-
 src/worker.c                | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/modules/example/module.conf b/modules/example/module.conf
index 014634c..a3724a4 100644
--- a/modules/example/module.conf
+++ b/modules/example/module.conf
@@ -12,7 +12,7 @@ runas		joris
 
 # Set workers to the amount of CPU's available in your system,
 # kore will automatically distribute all workers on them.
-workers		2
+workers		4
 
 # The number of active connections each worker can handle.
 # You might have to tweak this number based on your hardware.
diff --git a/src/worker.c b/src/worker.c
index e421d04..81158bb 100644
--- a/src/worker.c
+++ b/src/worker.c
@@ -340,7 +340,7 @@ kore_worker_acceptlock_obtain(void)
 	} else {
 		worker_has_acceptlock = 1;
 		kore_platform_enable_accept();
-		kore_log(LOG_NOTICE, "obtained accept lock (%d/%d)",
+		kore_debug("obtained accept lock (%d/%d)",
 		    worker_active_connections, worker_max_connections);
 	}
 }
@@ -363,7 +363,7 @@ kore_worker_acceptlock_release(void)
 	} else {
 		worker_has_acceptlock = 0;
 		kore_platform_disable_accept();
-		kore_log(LOG_NOTICE, "released %d/%d",
+		kore_debug("released %d/%d",
 		    worker_active_connections, worker_max_connections);
 	}
 }