From c1b2a434c08a992e980cc100e8b06feb5314c8e9 Mon Sep 17 00:00:00 2001 From: Francis Dupont Date: Fri, 12 Jan 2018 10:12:21 +0100 Subject: [PATCH] [5420] Added database logger rationale --- premium | 2 +- src/lib/dhcpsrv/db_log.h | 11 +++++++++++ 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/premium b/premium index 3894c2072c..0444698bce 160000 --- a/premium +++ b/premium @@ -1 +1 @@ -Subproject commit 3894c2072c2327af8c38dccaf26b1adfbdb45e35 +Subproject commit 0444698bce5984e7c6efc00e95993c8f707aecb3 diff --git a/src/lib/dhcpsrv/db_log.h b/src/lib/dhcpsrv/db_log.h index 1eb59a5caf..4eb76d6a0a 100644 --- a/src/lib/dhcpsrv/db_log.h +++ b/src/lib/dhcpsrv/db_log.h @@ -12,6 +12,17 @@ #include #include +/// @file db_log.h +/// +/// We want to reuse the database backend connection and exchange code +/// for other uses, in particular for hook libraries. But this code +/// includes some calls to the system logger for debug and uncommon +/// cases and of course we do not want to get log messages from +/// a hook library to seem to come from DHCP server core. +/// +/// The solution is to use a database logger which calls the right +/// logger with mapped messages. + namespace isc { namespace dhcp { -- 2.47.2