From: Mukund Sivaraman Date: Mon, 25 Jun 2012 18:32:04 +0000 (+0530) Subject: [2025] Rename message id and description X-Git-Tag: trac2351_base~213^2~6 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=84d243249151b4f949eb88ae16ded1e46f1f2943;p=thirdparty%2Fkea.git [2025] Rename message id and description This is done so there is no misunderstanding about whether b10-auth is processing NOTIFYs. --- diff --git a/src/bin/auth/auth_messages.mes b/src/bin/auth/auth_messages.mes index 0805d855fd..61de3ee0f5 100644 --- a/src/bin/auth/auth_messages.mes +++ b/src/bin/auth/auth_messages.mes @@ -110,8 +110,8 @@ look into the cause and address the issue. The log message includes the client's address (and port), and the error message sent from the lower layer that detects the failure. -% AUTH_PROCESS_NOTIFY processing incoming NOTIFY for zone name %1, zone class %2 -This is a debug message reporting that an incoming NOTIFY is being processed. +% AUTH_RECEIVED_NOTIFY received incoming NOTIFY for zone name %1, zone class %2 +This is a debug message reporting that an incoming NOTIFY was received. % AUTH_NOTIFY_QUESTIONS invalid number of questions (%1) in incoming NOTIFY This debug message is logged by the authoritative server when it receives diff --git a/src/bin/auth/auth_srv.cc b/src/bin/auth/auth_srv.cc index f06f0238cb..6563cb7c8a 100644 --- a/src/bin/auth/auth_srv.cc +++ b/src/bin/auth/auth_srv.cc @@ -828,7 +828,7 @@ AuthSrvImpl::processNotify(const IOMessage& io_message, Message& message, return (false); } - LOG_DEBUG(auth_logger, DBG_AUTH_DETAIL, AUTH_PROCESS_NOTIFY) + LOG_DEBUG(auth_logger, DBG_AUTH_DETAIL, AUTH_RECEIVED_NOTIFY) .arg(question->getName().toText()).arg(question->getClass().toText()); const string remote_ip_address = diff --git a/tests/lettuce/features/xfrin_notify_handling.feature b/tests/lettuce/features/xfrin_notify_handling.feature index 06bda77e92..2a445b6e8d 100644 --- a/tests/lettuce/features/xfrin_notify_handling.feature +++ b/tests/lettuce/features/xfrin_notify_handling.feature @@ -20,7 +20,7 @@ Feature: Xfrin incoming notify handling When I send bind10 with cmdctl port 47804 the command Xfrout notify example.org IN Then wait for new master stderr message XFROUT_NOTIFY_COMMAND - Then wait for new bind10 stderr message AUTH_PROCESS_NOTIFY + Then wait for new bind10 stderr message AUTH_RECEIVED_NOTIFY Then wait for new bind10 stderr message ZONEMGR_RECEIVE_NOTIFY Then wait for new bind10 stderr message XFRIN_XFR_TRANSFER_STARTED Then wait for new bind10 stderr message XFRIN_TRANSFER_SUCCESS not XFRIN_XFR_PROCESS_FAILURE