BIND 10 trac1858, updated. ae0565a4ed6e8a947120a7bfe826c1cf9d672760 [1858] (unrelated cleanup) removed BIND10_START_AS_NON_ROOT_AUTH log.

[BIND 10 source code commits]

The branch, trac1858 has been updated
       via  ae0565a4ed6e8a947120a7bfe826c1cf9d672760 (commit)
      from  2768eb3551fdaa2c4728563535dfb69f732dc033 (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 ae0565a4ed6e8a947120a7bfe826c1cf9d672760
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Fri Oct 12 13:48:46 2012 -0700

    [1858] (unrelated cleanup) removed BIND10_START_AS_NON_ROOT_AUTH log.
    
    with the introduction of socket creation this log message hasn't been
    making sense.  It would be rather confusing and harmful.

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

Summary of changes:
 src/bin/bind10/bind10_messages.mes |    7 -------
 src/bin/bind10/bind10_src.py.in    |    2 --
 2 files changed, 9 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/bin/bind10/bind10_messages.mes b/src/bin/bind10/bind10_messages.mes
index 6c3d12e..ed2a5d9 100644
--- a/src/bin/bind10/bind10_messages.mes
+++ b/src/bin/bind10/bind10_messages.mes
@@ -298,13 +298,6 @@ During the startup process, a number of messages are exchanged between the
 Boss process and the processes it starts.  This error is output when a
 message received by the Boss process is not recognised.
 
-% BIND10_START_AS_NON_ROOT_AUTH starting b10-auth as a user, not root. This might fail.
-The authoritative server is being started or restarted without root privileges.
-If the module needs these privileges, it may have problems starting.
-Note that this issue should be resolved by the pending 'socket-creator'
-process; once that has been implemented, modules should not need root
-privileges anymore. See tickets #800 and #801 for more information.
-
 % BIND10_START_AS_NON_ROOT_RESOLVER starting b10-resolver as a user, not root. This might fail.
 The resolver is being started or restarted without root privileges.
 If the module needs these privileges, it may have problems starting.
diff --git a/src/bin/bind10/bind10_src.py.in b/src/bin/bind10/bind10_src.py.in
index 7a245ae..45a2ccb 100755
--- a/src/bin/bind10/bind10_src.py.in
+++ b/src/bin/bind10/bind10_src.py.in
@@ -546,8 +546,6 @@ class BoB:
         """
             Start the Authoritative server
         """
-        if self.uid is not None and self.__started:
-            logger.warn(BIND10_START_AS_NON_ROOT_AUTH)
         authargs = ['b10-auth']
         if self.verbose:
             authargs += ['-v']