BIND 10 trac1522, updated. 17680761ae76b62e33c801732a2f86180d995cd0 [1522] normalize the log message file.

[BIND 10 source code commits]

The branch, trac1522 has been updated
       via  17680761ae76b62e33c801732a2f86180d995cd0 (commit)
      from  199ebdc9c9db2f7744bfc50f0b13eec40eeed5ed (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 17680761ae76b62e33c801732a2f86180d995cd0
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Fri Dec 30 01:11:51 2011 -0800

    [1522] normalize the log message file.

-----------------------------------------------------------------------

Summary of changes:
 src/lib/server_common/server_common_messages.mes |   50 +++++++++++-----------
 1 files changed, 25 insertions(+), 25 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/lib/server_common/server_common_messages.mes b/src/lib/server_common/server_common_messages.mes
index ababa08..01e424a 100644
--- a/src/lib/server_common/server_common_messages.mes
+++ b/src/lib/server_common/server_common_messages.mes
@@ -16,6 +16,31 @@ $NAMESPACE isc::server_common
 
 # \brief Messages for the server_common library
 
+% SOCKETREQUESTOR_CREATED Socket requestor created
+Debug message.  A socket requesor (client of the socket creator) is created
+for the corresponding application.  Normally this should happen at most
+one time throughout the lifetime of the application.
+
+% SOCKETREQUESTOR_DESTROYED Socket requestor destoryed
+Debug message.  The socket requestor created at SOCKETREQUESTOR_CREATED
+has been destroyed.  This event is generally unexpected other than in
+test cases.
+
+% SOCKETREQUESTOR_GETSOCKET Received a %1 socket for [%2]:%3, FD=%4, token=%5, path=%6
+Debug message. The socket requestor for the corresponding application
+has requested a socket for a set of address, port and protocol (shown
+in the log message) and successfully got it from the creator.  The
+corresponding file descriptor and the associated "token" (an internal
+ID used between the creator and requestor) are shown in the log
+message.
+
+% SOCKETREQUESTOR_RELEASESOCKET Released a socket of token %1
+Debug message.  The socket requestor has released a socket passed by
+the creator.  The associated token of the socket is shown in the
+log message.  If the corresponding SOCKETREQUESTOR_GETSOCKET was logged
+more detailed information of the socket can be identified by matching
+the token.
+
 % SRVCOMM_ADDRESSES_NOT_LIST the address and port specification is not a list in %1
 This points to an error in configuration. What was supposed to be a list of
 IP address - port pairs isn't a list at all but something else.
@@ -71,28 +96,3 @@ specification is outside the valid range of 0 to 65535.
 % SRVCOMM_SET_LISTEN setting addresses to listen to
 Debug message, noting that the server is about to start listening on a
 different set of IP addresses and ports than before.
-
-% SOCKETREQUESTOR_CREATED Socket requestor created
-Debug message.  A socket requesor (client of the socket creator) is created
-for the corresponding application.  Normally this should happen at most
-one time throughout the lifetime of the application.
-
-% SOCKETREQUESTOR_DESTROYED Socket requestor destoryed
-Debug message.  The socket requestor created at SOCKETREQUESTOR_CREATED
-has been destroyed.  This event is generally unexpected other than in
-test cases.
-
-% SOCKETREQUESTOR_GETSOCKET Received a %1 socket for [%2]:%3, FD=%4, token=%5, path=%6
-Debug message. The socket requestor for the corresponding application
-has requested a socket for a set of address, port and protocol (shown
-in the log message) and successfully got it from the creator.  The
-corresponding file descriptor and the associated "token" (an internal
-ID used between the creator and requestor) are shown in the log
-message.
-
-% SOCKETREQUESTOR_RELEASESOCKET Released a socket of token %1
-Debug message.  The socket requestor has released a socket passed by
-the creator.  The associated token of the socket is shown in the
-log message.  If the corresponding SOCKETREQUESTOR_GETSOCKET was logged
-more detailed information of the socket can be identified by matching
-the token.