Browse Source

[711] (unrelated cleanup) removed stale warn log about non root startup

it should have been removed much earlier.
JINMEI Tatuya 12 years ago
parent
commit
da5c7b1faa
2 changed files with 0 additions and 9 deletions
  1. 0 7
      src/bin/bind10/bind10_messages.mes
  2. 0 2
      src/bin/bind10/bind10_src.py.in

+ 0 - 7
src/bin/bind10/bind10_messages.mes

@@ -308,13 +308,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_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.
-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_STOP_PROCESS asking %1 to shut down
 The boss module is sending a shutdown command to the given module over
 the message channel.

+ 0 - 2
src/bin/bind10/bind10_src.py.in

@@ -626,8 +626,6 @@ class BoB:
             are pure speculation.  As with the auth daemon, they should be
             read from the configuration database.
         """
-        if self.__uid is not None and self.__started:
-            logger.warn(BIND10_START_AS_NON_ROOT_RESOLVER)
         self.curproc = "b10-resolver"
         # XXX: this must be read from the configuration manager in the future
         resargs = ['b10-resolver']