[1901] Replace 'boss' with 'b10-init' or 'b10_init'

doc/guide/bind10-guide.xml

@@ -1301,11 +1301,11 @@ Available module names:
 
         When 'help' is used as a command to a module, it shows the supported commands for the module; for example:
         <screen>&gt; <userinput>Boss help</userinput>
-Module  Boss 	Master process
+Module  Init 	Master process
 Available commands:
     help        Get help for module.
     shutdown    Shut down BIND 10
-    ping        Ping the boss process
+    ping        Ping the Init process
     show_processes
             List the running BIND 10 processes
         </screen>
@@ -2146,7 +2146,7 @@ AND_MATCH := "ALL": [ RULE_RAW, RULE_RAW, ... ]
             <row><entry>b10-auth</entry><entry>auth</entry><entry>Authoritative DNS server</entry></row>
             <row><entry>b10-resolver</entry><entry>resolver</entry><entry>DNS resolver</entry></row>
             <row><entry>b10-cmdctl</entry><entry>cmdctl</entry><entry>Command control (remote control interface)</entry></row>
-            <!-- TODO Either add xfrin and xfrout as well or clean up the workarounds in boss before the release -->
+            <!-- TODO Either add xfrin and xfrout as well or clean up the workarounds in b10-init before the release -->
           </tbody>
           </tgroup>
         </table>
@@ -2420,7 +2420,7 @@ can use various data source backends.
               <simpara>Stop the authoritative DNS server.
       This has an optional <varname>pid</varname> argument to
       select the process ID to stop.
-      (Note that the BIND 10 boss process may restart this service
+      (Note that the BIND 10 init process may restart this service
       if configured.)
               </simpara>
             </listitem>
@@ -3340,7 +3340,7 @@ then change those defaults with config set Resolver/forward_addresses[0]/address
     both servers.  DHCPv4-specific details are covered in <xref linkend="dhcp4"/>,
     while those details specific to DHCPv6 are described in <xref linkend="dhcp6"/>
     </para>
-    
+
     <section id="dhcp-install-configure">
       <title>DHCP Database Installation and Configuration</title>
       <para>
@@ -3409,7 +3409,7 @@ $</screen>
    </section>
 
   </chapter>
-  
+
   <chapter id="dhcp4">
     <title>The DHCPv4 Server</title>
 
@@ -3502,7 +3502,7 @@ Dhcp4/subnet4	[]	list	(default)
       The server comes with an in-memory database ("memfile") configured as the default
       database. This is used for internal testing and is not supported.  In addition,
       it does not store lease information on disk: lease information will be lost if the
-      server is restarted. 
+      server is restarted.
       </para>
       </footnote>, and so the server must be configured to
       access the correct database with the appropriate credentials.
@@ -3552,7 +3552,7 @@ Dhcp4/subnet4	[]	list	(default)
       database.  Improved password security will be added in a future version of BIND 10 DHCP</para>
       </note>
       </section>
-      
+
       <section id="dhcp4-address-config">
       <title>Configuration of Address Pools</title>
       <para>
@@ -3782,7 +3782,7 @@ Dhcp6/lease-database/name	""	string	(default)
 Dhcp6/lease-database/user	""	string	(default)
 Dhcp6/lease-database/host	""	string	(default)
 Dhcp6/lease-database/password	""	string	(default)
-Dhcp6/subnet6/	list	
+Dhcp6/subnet6/	list
 </screen>
       </para>
       <para>
@@ -3813,7 +3813,7 @@ Dhcp6/subnet6/	list
       The server comes with an in-memory database ("memfile") configured as the default
       database. This is used for internal testing and is not supported.  In addition,
       it does not store lease information on disk: lease information will be lost if the
-      server is restarted. 
+      server is restarted.
       </para>
       </footnote>, and so the server must be configured to
       access the correct database with the appropriate credentials.
@@ -3959,7 +3959,7 @@ Dhcp6/subnet6/	list
         lines for clarity.)
       </para>
     </section>
-       
+
       <section id="dhcp6-config-subnets">
         <title>Subnet Selection</title>
           <para>
@@ -3994,8 +3994,8 @@ Dhcp6/subnet6/	list
 &gt; <userinput>config commit</userinput>
 </screen>
         </para>
-      </section>    
-    
+      </section>
+
    </section>
 
     <section id="dhcp6-serverid">

src/bin/auth/b10-auth.xml

@@ -53,8 +53,8 @@
     <para>The <command>b10-auth</command> daemon provides the BIND 10
       authoritative DNS server.
       Normally it is started by the
-      <citerefentry><refentrytitle>bind10</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-      boss process.
+      <citerefentry><refentrytitle>b10-init</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+      process.
     </para>
 
     <para>
@@ -194,7 +194,7 @@
       <command>shutdown</command> exits <command>b10-auth</command>.
       This has an optional <varname>pid</varname> argument to
       select the process ID to stop.
-      (Note that the BIND 10 boss process may restart this service
+      (Note that the b10-init process may restart this service
       if configured.)
     </para>
 

src/bin/auth/main.cc

@@ -187,7 +187,7 @@ main(int argc, char* argv[]) {
         // We delay starting listening to new commands/config just before we
         // go into the main loop to avoid confusion due to mixture of
         // synchronous and asynchronous operations (this would happen in
-        // initial communication with the boss that takes place in
+        // initial communication with b10-init that takes place in
         // updateConfig() for listen_on and in initializing TSIG keys below).
         // Until then all operations on the CC session will take place
         // synchronously.

src/bin/bind10/b10-init.py.in

@@ -43,11 +43,14 @@ import os
 # from a directory relative to that, otherwise we use the ones
 # installed on the system
 if "B10_FROM_SOURCE" in os.environ:
-    SPECFILE_LOCATION = os.environ["B10_FROM_SOURCE"] + "/src/bin/bind10/bob.spec"
+    SPECFILE_LOCATION = os.environ["B10_FROM_SOURCE"] +\
+                        "/src/bin/bind10/init.spec"
 else:
     PREFIX = "@prefix@"
     DATAROOTDIR = "@datarootdir@"
-    SPECFILE_LOCATION = "@datadir@/@PACKAGE@/bob.spec".replace("${datarootdir}", DATAROOTDIR).replace("${prefix}", PREFIX)
+    SPECFILE_LOCATION = "@datadir@/@PACKAGE@/init.spec"\
+                         .replace("${datarootdir}", DATAROOTDIR)\
+                         .replace("${prefix}", PREFIX)
 
 import subprocess
 import signal
@@ -69,15 +72,15 @@ import isc.cc
 import isc.util.process
 import isc.net.parse
 import isc.log
-from isc.log_messages.bind10_messages import *
+from isc.log_messages.init_messages import *
 import isc.bind10.component
 import isc.bind10.special_component
 import isc.bind10.socket_cache
 import libutil_io_python
 import tempfile
 
-isc.log.init("b10-boss", buffer=True)
-logger = isc.log.Logger("boss")
+isc.log.init("b10-init", buffer=True)
+logger = isc.log.Logger("init")
 
 # Pending system-wide debug level definitions, the ones we
 # use here are hardcoded for now
@@ -147,7 +150,7 @@ class ProcessInfo:
         """Function used before running a program that needs to run as a
         different user."""
         # First, put us into a separate process group so we don't get
-        # SIGINT signals on Ctrl-C (the boss will shut everthing down by
+        # SIGINT signals on Ctrl-C (b10-init will shut everthing down by
         # other means).
         os.setpgrp()
 
@@ -161,7 +164,7 @@ class ProcessInfo:
         else:
             spawn_stderr = None
         # Environment variables for the child process will be a copy of those
-        # of the boss process with any additional specific variables given
+        # of the b10-init process with any additional specific variables given
         # on construction (self.env).
         spawn_env = copy.deepcopy(os.environ)
         spawn_env.update(self.env)
@@ -198,7 +201,7 @@ class BoB:
             Initialize the Boss of BIND. This is a singleton (only one can run).
 
             The msgq_socket_file specifies the UNIX domain socket file that the
-            msgq process listens on.  If verbose is True, then the boss reports
+            msgq process listens on.  If verbose is True, then b10-init reports
             what it is doing.
 
             Data path and config filename are passed through to config manager
@@ -287,7 +290,7 @@ class BoB:
         for comp in self.__core_components:
             if comp in comps:
                 raise Exception(comp + " is core component managed by " +
-                                "bind10 boss, do not set it")
+                                "b10-init, do not set it")
             comps[comp] = self.__core_components[comp]
         # Update the configuration
         self._component_configurator.reconfigure(comps)
@@ -313,7 +316,7 @@ class BoB:
                 # We use one-shot logger after setuid here.  This will
                 # detect any permission issue regarding logging due to the
                 # result of setuid at the earliest opportunity.
-                isc.log.Logger("boss").info(BIND10_SETUID, self.__uid)
+                isc.log.Logger("b10-init").info(BIND10_SETUID, self.__uid)
         except Exception as ex:
             raise ChangeUserError('failed to change user: ' + str(ex))
 
@@ -578,7 +581,7 @@ class BoB:
 
     def register_process(self, pid, component):
         """
-        Put another process into boss to watch over it.  When the process
+        Put another process into b10-init to watch over it.  When the process
         dies, the component.failed() is called with the exit code.
 
         It is expected the info is a isc.bind10.component.BaseComponent
@@ -741,7 +744,7 @@ class BoB:
         logger.info(BIND10_SHUTDOWN)
         # If ccsession is still there, inform rest of the system this module
         # is stopping. Since everything will be stopped shortly, this is not
-        # really necessary, but this is done to reflect that boss is also
+        # really necessary, but this is done to reflect that b10-init is also
         # 'just' a module.
         self.ccs.send_stopping()
 
@@ -943,7 +946,7 @@ class BoB:
 
     def set_creator(self, creator):
         """
-        Registeres a socket creator into the boss. The socket creator is not
+        Registeres a socket creator into the b10-init. The socket creator is not
         used directly, but through a cache. The cache is created in this
         method.
 
@@ -1078,7 +1081,7 @@ class BoB:
 
 # global variables, needed for signal handlers
 options = None
-boss_of_bind = None
+b10_init = None
 
 def reaper(signal_number, stack_frame):
     """A child process has died (SIGCHLD received)."""
@@ -1099,10 +1102,10 @@ def get_signame(signal_number):
 def fatal_signal(signal_number, stack_frame):
     """We need to exit (SIGINT or SIGTERM received)."""
     global options
-    global boss_of_bind
+    global b10_init
     logger.info(BIND10_RECEIVED_SIGNAL, get_signame(signal_number))
     signal.signal(signal.SIGCHLD, signal.SIG_DFL)
-    boss_of_bind.runnable = False
+    b10_init.runnable = False
 
 def process_rename(option, opt_str, value, parser):
     """Function that renames the process if it is requested by a option."""
@@ -1224,7 +1227,7 @@ def remove_lock_files():
 
 def main():
     global options
-    global boss_of_bind
+    global b10_init
     # Enforce line buffering on stdout, even when not a TTY
     sys.stdout = io.TextIOWrapper(sys.stdout.detach(), line_buffering=True)
 
@@ -1287,32 +1290,32 @@ def main():
 
     try:
         # Go bob!
-        boss_of_bind = BoB(options.msgq_socket_file, options.data_path,
+        b10_init = BoB(options.msgq_socket_file, options.data_path,
                            options.config_file, options.clear_config,
                            options.verbose, options.nokill,
                            setuid, setgid, username, options.cmdctl_port,
                            options.wait_time)
-        startup_result = boss_of_bind.startup()
+        startup_result = b10_init.startup()
         if startup_result:
             logger.fatal(BIND10_STARTUP_ERROR, startup_result)
             sys.exit(1)
-        boss_of_bind.init_socket_srv()
+        b10_init.init_socket_srv()
         logger.info(BIND10_STARTUP_COMPLETE)
         dump_pid(options.pid_file)
 
         # Let it run
-        boss_of_bind.run(wakeup_pipe[0])
+        b10_init.run(wakeup_pipe[0])
 
         # shutdown
         signal.signal(signal.SIGCHLD, signal.SIG_DFL)
-        boss_of_bind.shutdown()
+        b10_init.shutdown()
     finally:
         # Clean up the filesystem
         unlink_pid_file(options.pid_file)
         remove_lock_files()
-        if boss_of_bind is not None:
-            boss_of_bind.remove_socket_srv()
-    sys.exit(boss_of_bind.exitcode)
+        if b10_init is not None:
+            b10_init.remove_socket_srv()
+    sys.exit(b10_init.exitcode)
 
 if __name__ == "__main__":
     main()

src/bin/bind10/b10-init.xml

@@ -24,14 +24,14 @@
   </refentryinfo>
 
   <refmeta>
-    <refentrytitle>bind10</refentrytitle>
+    <refentrytitle>b10-init</refentrytitle>
     <manvolnum>8</manvolnum>
     <refmiscinfo>BIND10</refmiscinfo>
   </refmeta>
 
   <refnamediv>
-    <refname>bind10</refname>
-    <refpurpose>BIND 10 boss process</refpurpose>
+    <refname>b10-init</refname>
+    <refpurpose>BIND 10 init process</refpurpose>
   </refnamediv>
 
   <docinfo>
@@ -43,7 +43,7 @@
 
   <refsynopsisdiv>
     <cmdsynopsis>
-      <command>bind10</command>
+      <command>b10-init</command>
       <arg><option>-c <replaceable>config-filename</replaceable></option></arg>
       <arg><option>-i</option></arg>
       <arg><option>-m <replaceable>file</replaceable></option></arg>
@@ -68,14 +68,14 @@
   <refsect1>
     <title>DESCRIPTION</title>
 
-    <para>The <command>bind10</command> daemon starts up other
+    <para>The <command>b10-init</command> daemon starts up other
     BIND 10 required daemons.  It handles restarting of exiting
     programs and also the shutdown of all managed daemons.</para>
 
 <!-- TODO: list what it starts here? -->
 
 <!-- TODO
-    <para>The configuration of the <command>bind10</command> daemon
+    <para>The configuration of the <command>b10-init</command> daemon
     is defined in the TODO configuration file, as described in the
     <citerefentry><refentrytitle>TODO</refentrytitle><manvolnum>5</manvolnum></citerefentry>
     manual page.</para>
@@ -169,7 +169,7 @@
       <varlistentry>
         <term><option>-i</option>, <option>--no-kill</option></term>
         <listitem>
-	  <para>When this option is passed, <command>bind10</command>
+	  <para>When this option is passed, <command>b10-init</command>
 	  does not send SIGTERM and SIGKILL signals to modules during
 	  shutdown. (This option was introduced for use during
 	  testing.)</para>
@@ -180,8 +180,8 @@
         <term><option>-u</option> <replaceable>user</replaceable>, <option>--user</option> <replaceable>name</replaceable></term>
 <!-- TODO: example more detail. -->
         <listitem>
-          <para>The username for <command>bind10</command> to run as.
-            <command>bind10</command> must be initially ran as the
+          <para>The username for <command>b10-init</command> to run as.
+            <command>b10-init</command> must be initially ran as the
             root user to use this option.
             The default is to run as the current user.</para>
          </listitem>
@@ -190,7 +190,7 @@
       <varlistentry>
         <term><option>--pid-file</option> <replaceable>filename</replaceable></term>
         <listitem>
-          <para>If defined, the PID of the <command>bind10</command> is stored
+          <para>If defined, the PID of the <command>b10-init</command> is stored
              in this file.
           </para>
          </listitem>
@@ -203,7 +203,7 @@
           <para>The name this process should have in tools like
           <command>ps</command> or <command>top</command>. This
           is handy if you have multiple versions/installations
-          of <command>bind10</command>.
+          of <command>b10-init</command>.
 <!-- TODO: only supported with setproctitle feature
 The default is the basename of ARG 0.
 -->
@@ -215,7 +215,7 @@ The default is the basename of ARG 0.
         <term><option>-v</option>, <option>--verbose</option></term>
         <listitem>
 	  <para>Display more about what is going on for
-	  <command>bind10</command> and its child processes.</para>
+	  <command>b10-init</command> and its child processes.</para>
 <!-- TODO: not true about all children yet -->
         </listitem>
       </varlistentry>
@@ -245,7 +245,7 @@ TODO: configuration section
 
     <para>
       The configuration provides settings for components for
-      <command>bind10</command> to manage under
+      <command>b10-init</command> to manage under
       <varname>/Boss/components/</varname>.
       The default elements are:
     </para>
@@ -265,7 +265,7 @@ TODO: configuration section
     <para>
       (Note that the startup of <command>b10-sockcreator</command>,
       <command>b10-cfgmgr</command>, and <command>b10-msgq</command>
-      is not configurable. They are hardcoded and <command>bind10</command>
+      is not configurable. They are hardcoded and <command>b10-init</command>
       will not run without them.)
     </para>
 
@@ -296,12 +296,12 @@ sometime and I'd like it to teach to guess the address.
             This defines how required a component is.
             The possible settings for <varname>kind</varname> are:
             <varname>core</varname> (system won't start if it won't
-            start and <command>bind10</command> will shutdown if
+            start and <command>b10-init</command> will shutdown if
             a <quote>core</quote> component crashes),
-            <varname>dispensable</varname> (<command>bind10</command>
+            <varname>dispensable</varname> (<command>b10-init</command>
             will restart failing component),
             and
-	    <varname>needed</varname> (<command>bind10</command>
+	    <varname>needed</varname> (<command>b10-init</command>
 	    will shutdown if component won't initially start, but
 	    if crashes later, it will attempt to restart).
             This setting is required.
@@ -325,7 +325,7 @@ list
       <varlistentry>
         <term> <varname>priority</varname> </term>
         <listitem>
-          <para>This is an integer. <command>bind10</command>
+          <para>This is an integer. <command>b10-init</command>
             will start the components with largest priority numbers first.
           </para>
         </listitem>
@@ -335,7 +335,7 @@ list
           <term> <varname>process</varname> </term>
         <listitem>
           <para>This is the filename of the executable to be started.
-            If not defined, then <command>bind10</command> will
+            If not defined, then <command>b10-init</command> will
             use the component name instead.
           </para>
         </listitem>
@@ -368,9 +368,8 @@ xfrin
 
 <!-- TODO: formating -->
     <para>
-      The <varname>Boss</varname> configuration commands are:
+      The <varname>init</varname> configuration commands are:
     </para>
-<!-- TODO: let's just let bind10 be known as bind10 and not Boss -->
 
 <!-- TODO -->
 <!--
@@ -389,7 +388,7 @@ xfrin
 -->
 
     <para>
-      <command>getstats</command> tells <command>bind10</command>
+      <command>getstats</command> tells <command>b10-init</command>
       to send its statistics data to the <command>b10-stats</command>
       daemon.
       This is an internal command and not exposed to the administrator.
@@ -398,13 +397,13 @@ xfrin
 
     <para>
       <command>ping</command> is used to check the connection with the
-      <command>bind10</command> daemon.
+      <command>b10-init</command> daemon.
       It returns the text <quote>pong</quote>.
     </para>
 
     <para>
       <command>show_processes</command> lists the current processes
-      managed by <command>bind10</command>.
+      managed by <command>b10-init</command>.
       The output is an array in JSON format containing the process
       ID, the name for each and the address name used on each message bus.
 <!-- TODO: what is name? -->
@@ -413,10 +412,10 @@ xfrin
     </para>
 
     <para>
-      <command>shutdown</command> tells <command>bind10</command>
+      <command>shutdown</command> tells <command>b10-init</command>
       to shutdown the BIND 10 servers.
       It will tell each process it manages to shutdown and, when
-      complete, <command>bind10</command> will exit.
+      complete, <command>b10-init</command> will exit.
     </para>
 
   </refsect1>
@@ -434,7 +433,7 @@ xfrin
       <varlistentry>
         <term>boot_time</term>
         <listitem><para>
-          The date and time that the <command>bind10</command>
+          The date and time that the <command>b10-init</command>
           process started.
           This is represented in ISO 8601 format.
         </para></listitem>
@@ -493,14 +492,14 @@ xfrin
       </citerefentry>, -->
 
   <refsect1 id='history'><title>HISTORY</title>
-    <para>The development of <command>bind10</command>
+    <para>The development of <command>b10-init</command>
     was started in October 2009.</para>
   </refsect1>
 
   <refsect1>
     <title>AUTHORS</title>
     <para>
-      The <command>bind10</command>
+      The <command>b10-init</command>
       daemon was initially designed by Shane Kerr of ISC.
     </para>
   </refsect1>

src/bin/bind10/bind10

@@ -0,0 +1,3 @@
+#!/bin/sh
+BIND10_SBIN_DIR=`dirname $0`
+exec ${BIND10_SBIN_DIR}/b10-init $*

src/bin/bind10/creatorapi.txt

@@ -25,7 +25,7 @@ It seems we are stuck with current msgq for a while and there's a chance the
 new replacement will not be able to send sockets inbound. So, we need another
 channel.
 
-The boss will create a unix-domain socket and listen on it. When something
+b10-init will create a unix-domain socket and listen on it. When something
 requests a socket over the command channel and the socket is created, some kind
 of token is returned to the application (which will represent the future
 socket). The application then connects to the unix-domain socket, sends the
@@ -60,7 +60,7 @@ command channel), the reference count can be decreased without problems. But
 when the application terminates or crashes, we need to decrease it as well.
 There's a problem, since we don't know which command channel connection (eg.
 lname) belongs to which PID. Furthermore, the applications don't need to be
-started by boss.
+started by b10-init.
 
 There are two possibilities:
 * Let the msgq send messages about disconnected clients (eg. group message to
@@ -75,12 +75,12 @@ There are two possibilities:
 The commands
 ------------
 * Command to release a socket. This one would have single parameter, the token
-  used to get the socket. After this, boss would decrease its reference count
-  and if it drops to zero, close its own copy of the socket. This should be used
-  when the module stops using the socket (and after closes it). The
-  library could remember the file-descriptor to token mapping (for
-  common applications that don't request the same socket multiple
-  times in parallel).
+  used to get the socket. After this, b10-init would decrease its reference
+  count and if it drops to zero, close its own copy of the socket. This
+  should be used when the module stops using the socket (and after closes
+  it). The library could remember the file-descriptor to token mapping (for
+  common applications that don't request the same socket multiple times in
+  parallel).
 * Command to request a socket. It would have parameters to specify which socket
   (IP address, address family, port) and how to allow sharing. Sharing would be
   one of:

src/bin/bind10/init.spec

@@ -1,6 +1,6 @@
 {
   "module_spec": {
-    "module_name": "Boss",
+    "module_name": "Init",
     "module_description": "Master process",
     "config_data": [
       {
@@ -66,7 +66,7 @@
       },
       {
         "command_name": "ping",
-        "command_description": "Ping the boss process",
+        "command_description": "Ping the b10-init process",
         "command_args": []
       },
       {

src/bin/bind10/init_messages.mes

@@ -16,12 +16,12 @@
 # of the xfrin messages python module.
 
 % BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq is already running
-The boss process is starting up and will now check if the message bus
+The b10-init process is starting up and will now check if the message bus
 daemon is already running. If so, it will not be able to start, as it
 needs a dedicated message bus.
 
 % BIND10_COMPONENT_FAILED component %1 (pid %2) failed: %3
-The process terminated, but the bind10 boss didn't expect it to, which means
+The process terminated, but b10-init didn't expect it to, which means
 it must have failed.
 
 % BIND10_COMPONENT_RESTART component %1 is about to restart
@@ -30,7 +30,7 @@ as flawless service as possible, but it should be investigated what happened,
 as it could happen again.
 
 % BIND10_COMPONENT_START component %1 is starting
-The named component is about to be started by the boss process.
+The named component is about to be started by the b10-init process.
 
 % BIND10_COMPONENT_START_EXCEPTION component %1 failed to start: %2
 An exception (mentioned in the message) happened during the startup of the
@@ -38,7 +38,7 @@ named component. The componet is not considered started and further actions
 will be taken about it.
 
 % BIND10_COMPONENT_STOP component %1 is being stopped
-A component is about to be asked to stop willingly by the boss.
+A component is about to be asked to stop willingly by the b10-init.
 
 % BIND10_COMPONENT_UNSATISFIED component %1 is required to run and failed
 A component failed for some reason (see previous messages). It is either a core
@@ -59,31 +59,31 @@ will be propagated.
 A different configuration of which components should be running is being
 installed. All components that are no longer needed will be stopped and
 newly introduced ones started. This happens at startup, when the configuration
-is read the first time, or when an operator changes configuration of the boss.
+is read the first time, or when an operator changes configuration of the b10-init.
 
 % BIND10_CONFIGURATOR_RUN running plan of %1 tasks
 A debug message. The configurator is about to execute a plan of actions it
 computed previously.
 
 % BIND10_CONFIGURATOR_START bind10 component configurator is starting up
-The part that cares about starting and stopping the right component from the
-boss process is starting up. This happens only once at the startup of the
-boss process. It will start the basic set of processes now (the ones boss
-needs to read the configuration), the rest will be started after the
-configuration is known.
+The part that cares about starting and stopping the right component from
+the b10-init process is starting up. This happens only once at the startup
+of the b10-init process. It will start the basic set of processes now (the
+ones b10-init needs to read the configuration), the rest will be started
+after the configuration is known.
 
 % BIND10_CONFIGURATOR_STOP bind10 component configurator is shutting down
-The part that cares about starting and stopping processes in the boss is
+The part that cares about starting and stopping processes in the b10-init is
 shutting down. All started components will be shut down now (more precisely,
 asked to terminate by their own, if they fail to comply, other parts of
-the boss process will try to force them).
+the b10-init process will try to force them).
 
 % BIND10_CONFIGURATOR_TASK performing task %1 on %2
 A debug message. The configurator is about to perform one task of the plan it
 is currently executing on the named component.
 
 % BIND10_CONNECTING_TO_CC_FAIL failed to connect to configuration/command channel; try -v to see output from msgq
-The boss process tried to connect to the communication channel for
+The b10-init process tried to connect to the communication channel for
 commands and configuration updates during initialization, but it
 failed.  This is a fatal startup error, and process will soon
 terminate after some cleanup.  There can be several reasons for the
@@ -98,15 +98,15 @@ you specify the -u option to change process users, the directory must
 be writable for that user.
 
 % BIND10_INVALID_STATISTICS_DATA invalid specification of statistics data specified
-An error was encountered when the boss module specified
-statistics data which is invalid for the boss specification file.
+An error was encountered when the b10-init module specified
+statistics data which is invalid for the b10-init specification file.
 
 % BIND10_INVALID_USER invalid user: %1
-The boss process was started with the -u option, to drop root privileges
+The b10-init process was started with the -u option, to drop root privileges
 and continue running as the specified user, but the user is unknown.
 
 % BIND10_KILLING_ALL_PROCESSES killing all started processes
-The boss module was not able to start every process it needed to start
+The b10-init module was not able to start every process it needed to start
 during startup, and will now kill the processes that did get started.
 
 % BIND10_LOST_SOCKET_CONSUMER consumer %1 of sockets disconnected, considering all its sockets closed
@@ -136,28 +136,28 @@ This indicates a process started previously terminated. The process id
 and component owning the process are indicated, as well as the exit code.
 This doesn't distinguish if the process was supposed to terminate or not.
 
-% BIND10_READING_BOSS_CONFIGURATION reading boss configuration
-The boss process is starting up, and will now process the initial
+% BIND10_READING_BOSS_CONFIGURATION reading b10-init configuration
+The b10-init process is starting up, and will now process the initial
 configuration, as received from the configuration manager.
 
 % BIND10_RECEIVED_COMMAND received command: %1
-The boss module received a command and shall now process it. The command
+The b10-init module received a command and shall now process it. The command
 is printed.
 
 % BIND10_RECEIVED_NEW_CONFIGURATION received new configuration: %1
-The boss module received a configuration update and is going to apply
+The b10-init module received a configuration update and is going to apply
 it now. The new configuration is printed.
 
 % BIND10_RECEIVED_SIGNAL received signal %1
-The boss module received the given signal.
+The b10-init module received the given signal.
 
 % BIND10_RESTART_COMPONENT_SKIPPED Skipped restarting a component %1
-The boss module tried to restart a component after it failed (crashed)
-unexpectedly, but the boss then found that the component had been removed
+The b10-init module tried to restart a component after it failed (crashed)
+unexpectedly, but the b10-init then found that the component had been removed
 from its local configuration of components to run.  This is an unusual
 situation but can happen if the administrator removes the component from
 the configuration after the component's crash and before the restart time.
-The boss module simply skipped restarting that module, and the whole system
+The b10-init module simply skipped restarting that module, and the whole system
 went back to the expected state (except that the crash itself is likely
 to be a bug).
 
@@ -175,51 +175,51 @@ should not happen under normal circumstances and is considered fatal,
 so BIND 10 will now shut down. The specific error is printed.
 
 % BIND10_SEND_SIGKILL sending SIGKILL to %1 (PID %2)
-The boss module is sending a SIGKILL signal to the given process.
+The b10-init module is sending a SIGKILL signal to the given process.
 
 % BIND10_SEND_SIGNAL_FAIL sending %1 to %2 (PID %3) failed: %4
-The boss module sent a single (either SIGTERM or SIGKILL) to a process,
+The b10-init module sent a single (either SIGTERM or SIGKILL) to a process,
 but it failed due to some system level error.  There are two major cases:
-the target process has already terminated but the boss module had sent
+the target process has already terminated but the b10-init module had sent
 the signal before it noticed the termination.  In this case an error
 message should indicate something like "no such process".  This can be
-safely ignored.  The other case is that the boss module doesn't have
+safely ignored.  The other case is that the b10-init module doesn't have
 the privilege to send a signal to the process.  It can typically
-happen when the boss module started as a privileged process, spawned a
+happen when the b10-init module started as a privileged process, spawned a
 subprocess, and then dropped the privilege.  It includes the case for
-the socket creator when the boss process runs with the -u command line
-option.  In this case, the boss module simply gives up to terminate
+the socket creator when the b10-init process runs with the -u command line
+option.  In this case, the b10-init module simply gives up to terminate
 the process explicitly because it's unlikely to succeed by keeping
 sending the signal.  Although the socket creator is implemented so
-that it will terminate automatically when the boss process exits
+that it will terminate automatically when the b10-init process exits
 (and that should be the case for any other future process running with
 a higher privilege), but it's recommended to check if there's any
 remaining BIND 10 process if this message is logged.  For all other
-cases, the boss module will keep sending the signal until it confirms
+cases, the b10-init module will keep sending the signal until it confirms
 all child processes terminate.  Although unlikely, this could prevent
-the boss module from exiting, just keeping sending the signals.  So,
+the b10-init module from exiting, just keeping sending the signals.  So,
 again, it's advisable to check if it really terminates when this
 message is logged.
 
 % BIND10_SEND_SIGTERM sending SIGTERM to %1 (PID %2)
-The boss module is sending a SIGTERM signal to the given process.
+The b10-init module is sending a SIGTERM signal to the given process.
 
 % BIND10_SETGID setting GID to %1
-The boss switches the process group ID to the given value.  This happens
+The b10-init switches the process group ID to the given value.  This happens
 when BIND 10 starts with the -u option, and the group ID will be set to
 that of the specified user.
 
 % BIND10_SETUID setting UID to %1
-The boss switches the user it runs as to the given UID.
+The b10-init switches the user it runs as to the given UID.
 
 % BIND10_SHUTDOWN stopping the server
-The boss process received a command or signal telling it to shut down.
+The b10-init process received a command or signal telling it to shut down.
 It will send a shutdown command to each process. The processes that do
 not shut down will then receive a SIGTERM signal. If that doesn't work,
 it shall send SIGKILL signals to the processes still alive.
 
 % BIND10_SHUTDOWN_COMPLETE all processes ended, shutdown complete
-All child processes have been stopped, and the boss process will now
+All child processes have been stopped, and the b10-init process will now
 stop itself.
 
 % BIND10_SOCKCREATOR_BAD_CAUSE unknown error cause from socket creator: %1
@@ -227,7 +227,7 @@ The socket creator reported an error when creating a socket. But the function
 which failed is unknown (not one of 'S' for socket or 'B' for bind).
 
 % BIND10_SOCKCREATOR_BAD_RESPONSE unknown response for socket request: %1
-The boss requested a socket from the creator, but the answer is unknown. This
+The b10-init requested a socket from the creator, but the answer is unknown. This
 looks like a programmer error.
 
 % BIND10_SOCKCREATOR_EOF eof while expecting data from socket creator
@@ -235,7 +235,7 @@ There should be more data from the socket creator, but it closed the socket.
 It probably crashed.
 
 % BIND10_SOCKCREATOR_INIT initializing socket creator parser
-The boss module initializes routines for parsing the socket creator
+The b10-init module initializes routines for parsing the socket creator
 protocol.
 
 % BIND10_SOCKCREATOR_KILL killing the socket creator
@@ -243,7 +243,7 @@ The socket creator is being terminated the aggressive way, by sending it
 sigkill. This should not happen usually.
 
 % BIND10_SOCKCREATOR_TERMINATE terminating socket creator
-The boss module sends a request to terminate to the socket creator.
+The b10-init module sends a request to terminate to the socket creator.
 
 % BIND10_SOCKCREATOR_TRANSPORT_ERROR transport error when talking to the socket creator: %1
 Either sending or receiving data from the socket creator failed with the given
@@ -259,7 +259,7 @@ The socket creator failed to create the requested socket. It failed on the
 indicated OS API function with given error.
 
 % BIND10_SOCKET_GET requesting socket [%1]:%2 of type %3 from the creator
-The boss forwards a request for a socket to the socket creator.
+The b10-init forwards a request for a socket to the socket creator.
 
 % BIND10_STARTED_CC started configuration/command session
 Debug message given when BIND 10 has successfully started the object that
@@ -279,14 +279,14 @@ Informational message given when BIND 10 is starting the session object
 that handles configuration and commands.
 
 % BIND10_STARTING_PROCESS starting process %1
-The boss module is starting the given process.
+The b10-init module is starting the given process.
 
 % BIND10_STARTING_PROCESS_PORT starting process %1 (to listen on port %2)
-The boss module is starting the given process, which will listen on the
+The b10-init module is starting the given process, which will listen on the
 given port number.
 
 % BIND10_STARTING_PROCESS_PORT_ADDRESS starting process %1 (to listen on %2#%3)
-The boss module is starting the given process, which will listen on the
+The b10-init module is starting the given process, which will listen on the
 given address and port number (written as <address>#<port>).
 
 % BIND10_STARTUP_COMPLETE BIND 10 started
@@ -309,12 +309,12 @@ Boss process and the processes it starts.  This error is output when a
 message received by the Boss process is not recognised.
 
 % BIND10_STOP_PROCESS asking %1 to shut down
-The boss module is sending a shutdown command to the given module over
+The b10-init module is sending a shutdown command to the given module over
 the message channel.
 
 % BIND10_UNKNOWN_CHILD_PROCESS_ENDED unknown child pid %1 exited
 An unknown child process has exited. The PID is printed, but no further
-action will be taken by the boss process.
+action will be taken by the b10-init process.
 
 % BIND10_WAIT_CFGMGR waiting for configuration manager process to initialize
 The configuration manager process is so critical to operation of BIND 10

src/bin/bind10/run_bind10.sh.in

@@ -45,5 +45,5 @@ export B10_FROM_BUILD
 BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
 export BIND10_MSGQ_SOCKET_FILE
 
-exec ${PYTHON_EXEC} -O ${BIND10_PATH}/bind10 "$@"
+exec ${BIND10_PATH}/bind10 "$@"
 

src/bin/bind10/tests/args_test.py

@@ -1,5 +1,5 @@
 """
-This program tests the boss process to make sure that it runs while
+This program tests the b10-init process to make sure that it runs while
 dropping permissions. It must be run as a user that can set permission.
 """
 import unittest
@@ -22,12 +22,12 @@ class TestBossArgs(unittest.TestCase):
         found_string = False
         start_time = time.time()
         while time.time() < start_time + TIMEOUT:
-            (r,w,x) = select.select((bob.stdout,), (), (), TIMEOUT) 
+            (r,w,x) = select.select((bob.stdout,), (), (), TIMEOUT)
             if bob.stdout in r:
                 s = bob.stdout.readline()
                 if s == '':
                     break
-                if s.startswith(s): 
+                if s.startswith(s):
                     found_string = True
                     break
         return found_string

src/bin/bind10/tests/bind10_test.py.in

@@ -108,19 +108,19 @@ class TestProcessInfo(unittest.TestCase):
 
 class TestCacheCommands(unittest.TestCase):
     """
-    Test methods of boss related to the socket cache and socket handling.
+    Test methods of b10-init related to the socket cache and socket handling.
     """
     def setUp(self):
         """
-        Prepare the boss for some tests.
+        Prepare b10-init for some tests.
 
         Also prepare some variables we need.
         """
-        self.__boss = BoB()
+        self.__b10_init = BoB()
         # Fake the cache here so we can pretend it is us and hijack the
         # calls to its methods.
-        self.__boss._socket_cache = self
-        self.__boss._socket_path = '/socket/path'
+        self.__b10_init._socket_cache = self
+        self.__b10_init._socket_path = '/socket/path'
         self.__raise_exception = None
         self.__socket_args = {
             "port": 53,
@@ -178,18 +178,18 @@ class TestCacheCommands(unittest.TestCase):
         """
         Test that it calls the drop_application method of the cache.
         """
-        self.__boss.socket_consumer_dead(self.FalseSocket())
+        self.__b10_init.socket_consumer_dead(self.FalseSocket())
         self.assertEqual(42, self.__drop_app_called)
 
     def test_consumer_dead_invalid(self):
         """
         Test that it doesn't crash in case the application is not known to
-        the cache, the boss doesn't crash, as this actually can happen in
+        the cache, the b10_init doesn't crash, as this actually can happen in
         practice.
         """
         self.__raise_exception = ValueError("This application is unknown")
         # This doesn't crash
-        self.__boss.socket_consumer_dead(self.FalseSocket())
+        self.__b10_init.socket_consumer_dead(self.FalseSocket())
 
     def get_socket(self, token, application):
         """
@@ -210,7 +210,7 @@ class TestCacheCommands(unittest.TestCase):
         socket = self.FalseSocket()
         # An exception from the cache
         self.__raise_exception = ValueError("Test value error")
-        self.__boss.socket_request_handler(b"token", socket)
+        self.__b10_init.socket_request_handler(b"token", socket)
         # It was called, but it threw, so it is not noted here
         self.assertIsNone(self.__get_socket_called)
         self.assertEqual(b"0\n", socket.send)
@@ -219,7 +219,7 @@ class TestCacheCommands(unittest.TestCase):
         # Now prepare a valid scenario
         self.__raise_exception = None
         socket.send = b""
-        self.__boss.socket_request_handler(b"token", socket)
+        self.__b10_init.socket_request_handler(b"token", socket)
         self.assertEqual(b"1\n", socket.send)
         self.assertEqual((42, 13), self.__send_fd_called)
         self.assertEqual(("token", 42), self.__get_socket_called)
@@ -240,7 +240,7 @@ class TestCacheCommands(unittest.TestCase):
         """
         Test the successful scenario of getting a socket.
         """
-        result = self.__boss._get_socket(self.__socket_args)
+        result = self.__b10_init._get_socket(self.__socket_args)
         [code, answer] = result['result']
         self.assertEqual(0, code)
         self.assertEqual({
@@ -264,7 +264,7 @@ class TestCacheCommands(unittest.TestCase):
             The rest is not tested, as it is already checked in the
             test_get_socket_ok.
             """
-            [rcode, ranswer] = self.__boss._get_socket(args)['result']
+            [rcode, ranswer] = self.__b10_init._get_socket(args)['result']
             self.assertEqual(code, rcode)
             if code != 0:
                 # This should be an error message. The exact formatting
@@ -325,18 +325,18 @@ class TestCacheCommands(unittest.TestCase):
         """
         # This should be OK and just propagated to the call.
         self.assertEqual({"result": [0]},
-                         self.__boss.command_handler("drop_socket",
-                                                     {"token": "token"}))
+                         self.__b10_init.command_handler("drop_socket",
+                                                         {"token": "token"}))
         self.assertEqual("token", self.__drop_socket_called)
         self.__drop_socket_called = None
         # Missing parameter
         self.assertEqual({"result": [1, "Missing token parameter"]},
-                         self.__boss.command_handler("drop_socket", {}))
+                         self.__b10_init.command_handler("drop_socket", {}))
         self.assertIsNone(self.__drop_socket_called)
         # An exception is raised from within the cache
         self.__raise_exception = ValueError("Test error")
         self.assertEqual({"result": [1, "Test error"]},
-                         self.__boss.command_handler("drop_socket",
+                         self.__b10_init.command_handler("drop_socket",
                          {"token": "token"}))
 
 
@@ -378,7 +378,7 @@ class TestBoB(unittest.TestCase):
         self.__uid_set = None
         bob = BoB()
         bob.change_user()
-        # No gid/uid set in boss, nothing called.
+        # No gid/uid set in b10_init, nothing called.
         self.assertIsNone(self.__gid_set)
         self.assertIsNone(self.__uid_set)
 
@@ -615,10 +615,12 @@ class MockBob(BoB):
         self.get_process_exit_status_called = False
 
         class MockSockCreator(isc.bind10.component.Component):
-            def __init__(self, process, boss, kind, address=None, params=None):
-                isc.bind10.component.Component.__init__(self, process, boss,
-                                                        kind, 'SockCreator')
-                self._start_func = boss.start_creator
+            def __init__(self, process, b10_init, kind, address=None,
+                         params=None):
+                isc.bind10.component.Component.__init__(self, process,
+                                                        b10_init, kind,
+                                                        'SockCreator')
+                self._start_func = b10_init.start_creator
 
         specials = isc.bind10.special_component.get_specials()
         specials['sockcreator'] = MockSockCreator
@@ -1276,7 +1278,7 @@ class TestPIDFile(unittest.TestCase):
 
 class TestBossComponents(unittest.TestCase):
     """
-    Test the boss propagates component configuration properly to the
+    Test b10-init propagates component configuration properly to the
     component configurator and acts sane.
     """
     def setUp(self):
@@ -1445,7 +1447,7 @@ class TestBossComponents(unittest.TestCase):
 
     def test_kills(self):
         """
-        Test that the boss kills components which don't want to stop.
+        Test that b10-init kills components which don't want to stop.
         """
         self.__real_test_kill()
 
@@ -1465,7 +1467,7 @@ class TestBossComponents(unittest.TestCase):
 
     def test_nokill(self):
         """
-        Test that the boss *doesn't* kill components which don't want to
+        Test that b10-init *doesn't* kill components which don't want to
         stop, when asked not to (by passing the --no-kill option which
         sets bob.nokill to True).
         """
@@ -2142,14 +2144,14 @@ class TestBossComponents(unittest.TestCase):
 
 class SocketSrvTest(unittest.TestCase):
     """
-    This tests some methods of boss related to the unix domain sockets used
-    to transfer other sockets to applications.
+    This tests some methods of b10-init related to the unix domain sockets
+    used to transfer other sockets to applications.
     """
     def setUp(self):
         """
-        Create the boss to test, testdata and backup some functions.
+        Create the b10-init to test, testdata and backup some functions.
         """
-        self.__boss = BoB()
+        self.__b10_init = BoB()
         self.__select_backup = bind10_src.select.select
         self.__select_called = None
         self.__socket_data_called = None
@@ -2216,24 +2218,24 @@ class SocketSrvTest(unittest.TestCase):
 
     def __accept(self):
         """
-        Hijact the accept method of the boss.
+        Hijact the accept method of the b10-init.
 
-        Notes down it was called and stops the boss.
+        Notes down it was called and stops b10-init.
         """
         self.__accept_called = True
-        self.__boss.runnable = False
+        self.__b10_init.runnable = False
 
     def test_srv_accept_called(self):
         """
-        Test that the _srv_accept method of boss is called when the listening
-        socket is readable.
+        Test that the _srv_accept method of b10-init is called when the
+        listening socket is readable.
         """
-        self.__boss.runnable = True
-        self.__boss._srv_socket = self.__FalseSocket(self)
-        self.__boss._srv_accept = self.__accept
-        self.__boss.ccs = self.__CCS()
+        self.__b10_init.runnable = True
+        self.__b10_init._srv_socket = self.__FalseSocket(self)
+        self.__b10_init._srv_accept = self.__accept
+        self.__b10_init.ccs = self.__CCS()
         bind10_src.select.select = self.__select_accept
-        self.__boss.run(2)
+        self.__b10_init.run(2)
         # It called the accept
         self.assertTrue(self.__accept_called)
         # And the select had the right parameters
@@ -2243,39 +2245,39 @@ class SocketSrvTest(unittest.TestCase):
         """
         Test how the _srv_accept method works.
         """
-        self.__boss._srv_socket = self.__FalseSocket(self)
-        self.__boss._srv_accept()
+        self.__b10_init._srv_socket = self.__FalseSocket(self)
+        self.__b10_init._srv_accept()
         # After we accepted, a new socket is added there
-        socket = self.__boss._unix_sockets[13][0]
+        socket = self.__b10_init._unix_sockets[13][0]
         # The socket is properly stored there
         self.assertTrue(isinstance(socket, self.__FalseSocket))
         # And the buffer (yet empty) is there
-        self.assertEqual({13: (socket, b'')}, self.__boss._unix_sockets)
+        self.assertEqual({13: (socket, b'')}, self.__b10_init._unix_sockets)
 
     def __socket_data(self, socket):
-        self.__boss.runnable = False
+        self.__b10_init.runnable = False
         self.__socket_data_called = socket
 
     def test_socket_data(self):
         """
         Test that a socket that wants attention gets it.
         """
-        self.__boss._srv_socket = self.__FalseSocket(self)
-        self.__boss._socket_data = self.__socket_data
-        self.__boss.ccs = self.__CCS()
-        self.__boss._unix_sockets = {13: (self.__FalseSocket(self, 13), b'')}
-        self.__boss.runnable = True
+        self.__b10_init._srv_socket = self.__FalseSocket(self)
+        self.__b10_init._socket_data = self.__socket_data
+        self.__b10_init.ccs = self.__CCS()
+        self.__b10_init._unix_sockets = {13: (self.__FalseSocket(self, 13), b'')}
+        self.__b10_init.runnable = True
         bind10_src.select.select = self.__select_data
-        self.__boss.run(2)
+        self.__b10_init.run(2)
         self.assertEqual(13, self.__socket_data_called)
         self.assertEqual(([2, 1, 42, 13], [], [], None), self.__select_called)
 
     def __prepare_data(self, data):
         socket = self.__FalseSocket(self, 13)
-        self.__boss._unix_sockets = {13: (socket, b'')}
+        self.__b10_init._unix_sockets = {13: (socket, b'')}
         socket.data = data
-        self.__boss.socket_consumer_dead = self.__consumer_dead
-        self.__boss.socket_request_handler = self.__socket_request_handler
+        self.__b10_init.socket_consumer_dead = self.__consumer_dead
+        self.__b10_init.socket_request_handler = self.__socket_request_handler
         return socket
 
     def __consumer_dead(self, socket):
@@ -2290,9 +2292,9 @@ class SocketSrvTest(unittest.TestCase):
         when it is closed.
         """
         socket = self.__prepare_data(None)
-        self.__boss._socket_data(13)
+        self.__b10_init._socket_data(13)
         self.assertEqual(socket, self.__consumer_dead_called)
-        self.assertEqual({}, self.__boss._unix_sockets)
+        self.assertEqual({}, self.__b10_init._unix_sockets)
         self.assertTrue(socket.closed)
 
     def test_socket_short(self):
@@ -2301,8 +2303,8 @@ class SocketSrvTest(unittest.TestCase):
         kept there, but nothing is called.
         """
         socket = self.__prepare_data(b'tok')
-        self.__boss._socket_data(13)
-        self.assertEqual({13: (socket, b'tok')}, self.__boss._unix_sockets)
+        self.__b10_init._socket_data(13)
+        self.assertEqual({13: (socket, b'tok')}, self.__b10_init._unix_sockets)
         self.assertFalse(socket.closed)
         self.assertIsNone(self.__consumer_dead_called)
         self.assertIsNone(self.__socket_request_handler_called)
@@ -2315,9 +2317,9 @@ class SocketSrvTest(unittest.TestCase):
         """
         socket = self.__prepare_data(b"en\nanothe")
         # The data to finish
-        self.__boss._unix_sockets[13] = (socket, b'tok')
-        self.__boss._socket_data(13)
-        self.assertEqual({13: (socket, b'anothe')}, self.__boss._unix_sockets)
+        self.__b10_init._unix_sockets[13] = (socket, b'tok')
+        self.__b10_init._socket_data(13)
+        self.assertEqual({13: (socket, b'anothe')}, self.__b10_init._unix_sockets)
         self.assertFalse(socket.closed)
         self.assertIsNone(self.__consumer_dead_called)
         self.assertEqual((b'token', socket),
@@ -2330,9 +2332,9 @@ class SocketSrvTest(unittest.TestCase):
         """
         sock = self.__prepare_data(socket.error(errno.ENOMEM,
             "There's more memory available, but not for you"))
-        self.__boss._socket_data(13)
+        self.__b10_init._socket_data(13)
         self.assertEqual(sock, self.__consumer_dead_called)
-        self.assertEqual({}, self.__boss._unix_sockets)
+        self.assertEqual({}, self.__b10_init._unix_sockets)
         self.assertTrue(sock.closed)
 
 class TestFunctions(unittest.TestCase):
@@ -2407,13 +2409,13 @@ class TestFunctions(unittest.TestCase):
         self.assertEqual('Unknown signal 59426', signame)
 
     def test_fatal_signal(self):
-        self.assertIsNone(bind10_src.boss_of_bind)
-        bind10_src.boss_of_bind = BoB()
-        bind10_src.boss_of_bind.runnable = True
+        self.assertIsNone(bind10_src.b10_init)
+        bind10_src.b10_init = BoB()
+        bind10_src.b10_init.runnable = True
         bind10_src.fatal_signal(signal.SIGTERM, None)
         # Now, runnable must be False
-        self.assertFalse(bind10_src.boss_of_bind.runnable)
-        bind10_src.boss_of_bind = None
+        self.assertFalse(bind10_src.b10_init.runnable)
+        bind10_src.b10_init = None
 
 if __name__ == '__main__':
     # store os.environ for test_unchanged_environment

src/bin/cfgmgr/b10-cfgmgr.py.in

@@ -115,7 +115,7 @@ def main():
         cm.read_config()
         for ppath in PLUGIN_PATHS:
             load_plugins(ppath, cm)
-        cm.notify_boss()
+        cm.notify_b10_init()
         cm.run()
     except SessionError as se:
         logger.fatal(CFGMGR_CC_SESSION_ERROR, se)

src/bin/cfgmgr/tests/b10-cfgmgr_test.py.in

@@ -27,7 +27,7 @@ class MyConfigManager:
     def __init__(self, path, filename, session=None, rename_config_file=False):
         self._path = path
         self.read_config_called = False
-        self.notify_boss_called = False
+        self.notify_b10_init_called = False
         self.run_called = False
         self.write_config_called = False
         self.rename_config_called = False
@@ -37,8 +37,8 @@ class MyConfigManager:
     def read_config(self):
         self.read_config_called = True
 
-    def notify_boss(self):
-        self.notify_boss_called = True
+    def notify_b10_init(self):
+        self.notify_b10_init_called = True
 
     def run(self):
         self.run_called = True
@@ -89,7 +89,7 @@ class TestConfigManagerStartup(unittest.TestCase):
         b.load_plugins = orig_load
 
         self.assertTrue(b.cm.read_config_called)
-        self.assertTrue(b.cm.notify_boss_called)
+        self.assertTrue(b.cm.notify_b10_init_called)
         self.assertTrue(b.cm.run_called)
         self.assertTrue(self.loaded_plugins)
         # if there are no changes, config is not written

src/bin/cmdctl/b10-cmdctl.xml

@@ -78,7 +78,7 @@
 
   <refsect1>
     <title>OPTIONS</title>
-    
+
     <para>The arguments are as follows:</para>
 
     <variablelist>
@@ -175,7 +175,7 @@
       <command>shutdown</command> exits <command>b10-cmdctl</command>.
       This has an optional <varname>pid</varname> argument to
       select the process ID to stop.
-      (Note that the BIND 10 boss process may restart this service
+      (Note that the b10-init process may restart this service
       if configured.)
     </para>
 

src/bin/cmdctl/cmdctl.py.in

@@ -339,7 +339,7 @@ class CommandControl():
                     self.modules_spec[args[0]] = args[1]
 
         elif command == ccsession.COMMAND_SHUTDOWN:
-            #When cmdctl get 'shutdown' command from boss,
+            #When cmdctl get 'shutdown' command from b10-init,
             #shutdown the outer httpserver.
             self._module_cc.send_stopping()
             self._httpserver.shutdown()

src/bin/ddns/b10-ddns.xml

@@ -56,8 +56,8 @@
     <para>The <command>b10-ddns</command> daemon provides the BIND 10
       Dynamic Update (DDNS) service, as specified in RFC 2136.
       Normally it is started by the
-      <citerefentry><refentrytitle>bind10</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-      boss process.
+      <citerefentry><refentrytitle>b10-init</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+      process.
     </para>
 
     <para>
@@ -154,7 +154,7 @@
       <command>shutdown</command> exits <command>b10-ddns</command>.
       This has an optional <varname>pid</varname> argument to
       select the process ID to stop.
-      (Note that the BIND 10 boss process may restart this service
+      (Note that the b10-init process may restart this service
       if configured.)
     </para>
 

src/bin/dhcp4/ctrl_dhcp4_srv.h

@@ -49,7 +49,7 @@ public:
     /// @brief Establishes msgq session.
     ///
     /// Creates session that will be used to receive commands and updated
-    /// configuration from boss (or indirectly from user via bindctl).
+    /// configuration from cfgmgr (or indirectly from user via bindctl).
     void establishSession();
 
     /// @brief Terminates existing msgq session.

src/bin/dhcp6/ctrl_dhcp6_srv.h

@@ -49,7 +49,7 @@ public:
     /// @brief Establishes msgq session.
     ///
     /// Creates session that will be used to receive commands and updated
-    /// configuration from boss (or indirectly from user via bindctl).
+    /// configuration from cfgmgr (or indirectly from user via bindctl).
     void establishSession();
 
     /// @brief Terminates existing msgq session.

src/bin/resolver/b10-resolver.xml

@@ -52,8 +52,8 @@
     <title>DESCRIPTION</title>
     <para>The <command>b10-resolver</command> daemon provides the BIND 10
       recursive DNS server.  Normally it is started by the
-      <citerefentry><refentrytitle>bind10</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-      boss process.
+      <citerefentry><refentrytitle>b10-init</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+      process.
     </para>
 
     <para>
@@ -205,7 +205,7 @@ once that is merged you can for instance do 'config add Resolver/forward_address
       <command>shutdown</command> exits <command>b10-resolver</command>.
       This has an optional <varname>pid</varname> argument to
       select the process ID to stop.
-      (Note that the BIND 10 boss process may restart this service
+      (Note that the b10-init process may restart this service
       if configured.)
     </para>
 

src/bin/stats/b10-stats-httpd.xml

@@ -54,7 +54,7 @@
       intended for HTTP/XML interface for statistics module. This server
       process runs as a process separated from the process of the BIND 10 Stats
       daemon (<command>b10-stats</command>). The server is initially executed
-      by the BIND 10 boss process (<command>bind10</command>) and eventually
+      by the b10-init process (<command>bind10</command>) and eventually
       exited by it.  The server is intended to serve requests by HTTP
       clients like web browsers and third-party modules. When the server is
       asked, it requests BIND 10 statistics data or its schema from
@@ -176,7 +176,7 @@
 	    exits the <command>b10-stats-httpd</command> process.
             This has an optional <varname>pid</varname> argument to
             select the process ID to stop.
-            (Note that the BIND 10 boss process may restart this service
+            (Note that the b10-init process may restart this service
             if configured.)
           </para>
         </listitem>

src/bin/stats/b10-stats.xml

@@ -131,7 +131,7 @@
       <command>b10-stats</command> process.
       This has an optional <varname>pid</varname> argument to
       select the process ID to stop.
-      (Note that the BIND 10 boss process may restart this service
+      (Note that the b10-init process may restart this service
       if configured.)
     </para>
 

src/bin/stats/stats.spec

@@ -92,7 +92,7 @@
         "item_optional": false,
         "item_default": "1970-01-01T00:00:00Z",
         "item_title": "Last update time",
-        "item_description": "The latest date time when the stats module receives from other modules like auth server or boss process and so on",
+        "item_description": "The latest date time when the stats module receives from other modules like auth server or b10-init process and so on",
         "item_format": "date-time"
       },
       {

src/bin/stats/tests/b10-stats_test.py

@@ -659,7 +659,7 @@ class TestStats(unittest.TestCase):
         self.assertEqual(self.stats.statistics_data['Auth']['queries.udp'], sum_qudp)
         self.assertTrue('Auth' in self.stats.statistics_data_bymid)
         # restore statistics data of killed auth
-        # self.base.boss.server.pid_list = [ killed ] + self.base.boss.server.pid_list[:]
+        # self.base.b10_init.server.pid_list = [ killed ] + self.base.b10_init.server.pid_list[:]
         self.stats.update_statistics_data('Auth',
                                           "bar1@foo",
                                           {'queries.tcp': bar1_tcp})
@@ -1151,9 +1151,9 @@ class TestStats(unittest.TestCase):
             send_command('show', 'Stats'),
             (0, stat.statistics_data))
         # check statistics data of 'Boss'
-        boss = self.base.boss.server
+        b10_init = self.base.b10_init.server
         self.assertEqual(
-            stat.statistics_data_bymid['Boss'][boss.cc_session.lname],
+            stat.statistics_data_bymid['Boss'][b10_init.cc_session.lname],
             {'boot_time': self.const_datetime})
         self.assertEqual(
             len(stat.statistics_data_bymid['Boss']), 1)
@@ -1219,8 +1219,8 @@ class TestStats(unittest.TestCase):
 
     def test_polling2(self):
         # set invalid statistics
-        boss = self.base.boss.server
-        boss.statistics_data = {'boot_time':1}
+        b10_init = self.base.b10_init.server
+        b10_init.statistics_data = {'boot_time':1}
         stats_server = ThreadingServerManager(MyStats)
         stat = stats_server.server
         stats_server.run()

src/bin/stats/tests/test_utils.py

@@ -210,7 +210,7 @@ class MockBoss:
       },
       {
         "command_name": "ping",
-        "command_description": "Ping the boss process",
+        "command_description": "Ping the b10-init process",
         "command_args": []
       },
       {
@@ -538,8 +538,8 @@ class BaseModules:
         self.cfgmgr = ThreadingServerManager(MockCfgmgr)
         self.cfgmgr.run()
         # MockBoss
-        self.boss = ThreadingServerManager(MockBoss)
-        self.boss.run()
+        self.b10_init = ThreadingServerManager(MockBoss)
+        self.b10_init.run()
         # MockAuth
         self.auth = ThreadingServerManager(MockAuth)
         self.auth.run()
@@ -559,7 +559,7 @@ class BaseModules:
         self.auth2.shutdown(True)
         self.auth.shutdown(True)
         # MockBoss
-        self.boss.shutdown(True)
+        self.b10_init.shutdown(True)
         # MockCfgmgr
         self.cfgmgr.shutdown(True)
         # remove the unused socket file

src/bin/xfrin/b10-xfrin.xml

@@ -56,8 +56,8 @@
     <para>The <command>b10-xfrin</command> daemon provides the BIND 10
       incoming DNS zone transfer service.
       Normally it is started by the
-      <citerefentry><refentrytitle>bind10</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-      boss process.
+      <citerefentry><refentrytitle>b10-init</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+      process.
       When triggered it can request and receive a zone transfer and store
       the zone in a BIND 10 zone data source.
     </para>
@@ -180,8 +180,8 @@ in separate zonemgr process.
 
     <para>
       <command>shutdown</command> stops all incoming zone transfers
-      and exits <command>b10-xfrin</command>. (Note that the BIND 10
-      boss process will restart this service.)
+      and exits <command>b10-xfrin</command>. (Note that the
+      b10-init process will restart this service.)
     </para>
 <!-- TODO:
 add a usage example of xfrin -->

src/bin/xfrout/b10-xfrout.xml

@@ -55,8 +55,8 @@
       outgoing DNS zone transfer service using AXFR or IXFR.
       It is also used to send outgoing NOTIFY messages.
       Normally it is started by the
-      <citerefentry><refentrytitle>bind10</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-      boss process.
+      <citerefentry><refentrytitle>b10-init</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+      process.
       When the <command>b10-auth</command> DNS server receives
       a transfer request, <command>b10-xfrout</command> sends the
       zone as found in the BIND 10 zone data store.
@@ -147,7 +147,7 @@
       and exits <command>b10-xfrout</command>.
       This has an optional <varname>pid</varname> argument to
       select the process ID to stop.
-      (Note that the BIND 10 boss process may restart this service
+      (Note that the BIND 10 b10-init process may restart this service
       if configured.)
     </para>
 

src/bin/zonemgr/b10-zonemgr.xml

@@ -55,8 +55,8 @@
       as the BIND 10 secondary manager, keeps track of timers
       and other information necessary for BIND 10 to act as a DNS slave.
       Normally it is started by the
-      <citerefentry><refentrytitle>bind10</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-      boss process.
+      <citerefentry><refentrytitle>b10-init</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+      process.
     </para>
 
     <para>
@@ -74,7 +74,7 @@
 
 <!--
 
-            self._send_command(XFRIN_MODULE_NAME, ZONE_NOTIFY_COMMAND, param) 
+            self._send_command(XFRIN_MODULE_NAME, ZONE_NOTIFY_COMMAND, param)
             self._clear_zone_notifier_master(zone_name_class)
         # Send refresh command to xfrin module
         else:
@@ -188,7 +188,7 @@
       <command>shutdown</command> exits <command>b10-zonemgr</command>.
       This has an optional <varname>pid</varname> argument to
       select the process ID to stop.
-      (Note that the BIND 10 boss process may restart this service
+      (Note that the b10-init process may restart this service
       if configured.)
     </para>
 

src/lib/python/bind10_config.py.in

@@ -43,8 +43,8 @@ def reload():
     #  the system.
     # PLUGIN_PATHS: configuration modules that are not associated to specific
     #  process
-    # LIBEXECPATH: Paths to programs invoked by the boss process
-    #  The boss process (directly or via a helper module) uses this as
+    # LIBEXECPATH: Paths to programs invoked by the b10-init process
+    #  The b10-init process (directly or via a helper module) uses this as
     #  the prefererred PATH before starting a child process.
     #  When "FROM_SOURCE", it lists the directories where the programs are
     #  built so that when BIND 10 is experimentally started on the source
@@ -53,7 +53,7 @@ def reload():
     # B10_FROM_SOURCE_LOCALSTATEDIR is specifically intended to be used for
     # tests where we want to use various types of configuration within the test
     # environment.  (We may want to make it even more generic so that the path
-    # is passed from the boss process)
+    # is passed from the b10-init process)
     if "B10_FROM_SOURCE" in os.environ:
         if "B10_FROM_SOURCE_LOCALSTATEDIR" in os.environ:
             DATA_PATH = os.environ["B10_FROM_SOURCE_LOCALSTATEDIR"]

src/lib/python/isc/bind10/component.py

@@ -28,12 +28,12 @@ configuration). This is yet to be designed.
 """
 
 import isc.log
-from isc.log_messages.bind10_messages import *
+from isc.log_messages.init_messages import *
 import time
 import os
 import signal
 
-logger = isc.log.Logger("boss")
+logger = isc.log.Logger("init")
 DBG_TRACE_DATA = 20
 DBG_TRACE_DETAILED = 80
 
@@ -96,13 +96,13 @@ class BaseComponent:
     that is already shutting down, impossible to stop, etc. We need to add more
     states in future to handle it properly.
     """
-    def __init__(self, boss, kind):
+    def __init__(self, b10_init, kind):
         """
         Creates the component in not running mode.
 
         The parameters are:
-        - `boss` the boss object to plug into. The component needs to plug
-          into it to know when it failed, etc.
+        - `b10_init` the b10_init object to plug into. The component needs
+           to plug into it to know when it failed, etc.
         - `kind` is the kind of component. It may be one of:
           * 'core' means the system can't run without it and it can't be
             safely restarted. If it does not start, the system is brought
@@ -127,7 +127,7 @@ class BaseComponent:
         Note that the __init__ method of child class should have these
         parameters:
 
-        __init__(self, process, boss, kind, address=None, params=None)
+        __init__(self, process, b10_init, kind, address=None, params=None)
 
         The extra parameters are:
         - `process` - which program should be started.
@@ -153,7 +153,7 @@ class BaseComponent:
             raise ValueError('Component kind can not be ' + kind)
         self.__state = STATE_STOPPED
         self._kind = kind
-        self._boss = boss
+        self._b10_init = b10_init
         self._original_start_time = None
 
     def start(self):
@@ -204,13 +204,14 @@ class BaseComponent:
 
     def failed(self, exit_code):
         """
-        Notify the component it crashed. This will be called from boss object.
+        Notify the component it crashed. This will be called from b10_init
+        object.
 
         If you try to call failed on a component that is not running,
         a ValueError is raised.
 
         If it is a core component or needed component and it was started only
-        recently, the component will become dead and will ask the boss to shut
+        recently, the component will become dead and will ask b10_init to shut
         down with error exit status. A dead component can't be started again.
 
         Otherwise the component will try to restart.
@@ -253,7 +254,7 @@ class BaseComponent:
              self._original_start_time):
             self.__state = STATE_DEAD
             logger.fatal(BIND10_COMPONENT_UNSATISFIED, self.name())
-            self._boss.component_shutdown(1)
+            self._b10_init.component_shutdown(1)
             return False
         # This means we want to restart
         else:
@@ -326,7 +327,7 @@ class BaseComponent:
         should be registered).
 
         You should register all the processes created by calling
-        self._boss.register_process.
+        self._b10_init.register_process.
         """
         pass
 
@@ -407,15 +408,15 @@ class Component(BaseComponent):
     directly. It is not recommended to override methods of this class
     on one-by-one basis.
     """
-    def __init__(self, process, boss, kind, address=None, params=None,
+    def __init__(self, process, b10_init, kind, address=None, params=None,
                  start_func=None):
         """
         Creates the component in not running mode.
 
         The parameters are:
         - `process` is the name of the process to start.
-        - `boss` the boss object to plug into. The component needs to plug
-          into it to know when it failed, etc.
+        - `b10_init` the b10-init object to plug into. The component needs to
+          plug into it to know when it failed, etc.
         - `kind` is the kind of component. Refer to the documentation of
           BaseComponent for details.
         - `address` is the address on message bus. It is used to ask it to
@@ -429,7 +430,7 @@ class Component(BaseComponent):
            There's a sensible default if not provided, which just launches
            the program without any special care.
         """
-        BaseComponent.__init__(self, boss, kind)
+        BaseComponent.__init__(self, b10_init, kind)
         self._process = process
         self._start_func = start_func
         self._address = address
@@ -443,25 +444,26 @@ class Component(BaseComponent):
         process and return the procinfo object describing the running process.
 
         If you don't provide the _start_func, the usual startup by calling
-        boss.start_simple is performed.
+        b10_init.start_simple is performed.
         """
         # This one is not tested. For one, it starts a real process
         # which is out of scope of unit tests, for another, it just
-        # delegates the starting to other function in boss (if a derived
+        # delegates the starting to other function in b10_init (if a derived
         # class does not provide an override function), which is tested
         # by use.
         if self._start_func is not None:
             procinfo = self._start_func()
         else:
             # TODO Handle params, etc
-            procinfo = self._boss.start_simple(self._process)
+            procinfo = self._b10_init.start_simple(self._process)
         self._procinfo = procinfo
-        self._boss.register_process(self.pid(), self)
+        self._b10_init.register_process(self.pid(), self)
 
     def _stop_internal(self):
-        self._boss.stop_process(self._process, self._address, self.pid())
+        self._b10_init.stop_process(self._process, self._address, self.pid())
         # TODO Some way to wait for the process that doesn't want to
-        # terminate and kill it would prove nice (or add it to boss somewhere?)
+        # terminate and kill it would prove nice (or add it to b10_init
+        # somewhere?)
 
     def name(self):
         """
@@ -498,7 +500,7 @@ class Configurator:
     b10-auth as core, it is safe to stop that one.
 
     The parameters are:
-    * `boss`: The boss we are managing for.
+    * `b10_init`: The b10-init we are managing for.
     * `specials`: Dict of specially started components. Each item is a class
       representing the component.
 
@@ -527,13 +529,14 @@ class Configurator:
       priority are started before the ones with lower priority. If it is
       not present, it defaults to 0.
     """
-    def __init__(self, boss, specials = {}):
+    def __init__(self, b10_init, specials = {}):
         """
         Initializes the configurator, but nothing is started yet.
 
-        The boss parameter is the boss object used to start and stop processes.
+        The b10_init parameter is the b10-init object used to start and stop
+        processes.
         """
-        self.__boss = boss
+        self.__b10_init = b10_init
         # These could be __private, but as we access them from within unittest,
         # it's more comfortable to have them just _protected.
 
@@ -551,7 +554,7 @@ class Configurator:
     def startup(self, configuration):
         """
         Starts the first set of processes. This configuration is expected
-        to be hardcoded from the boss itself to start the configuration
+        to be hardcoded from the b10-init itself to start the configuration
         manager and other similar things.
         """
         if self._running:
@@ -642,7 +645,7 @@ class Configurator:
                     # TODO: Better error handling
                     creator = self.__specials[component_config['special']]
                 component = creator(component_config.get('process', cname),
-                                    self.__boss, component_config['kind'],
+                                    self.__b10_init, component_config['kind'],
                                     component_config.get('address'),
                                     component_config.get('params'))
                 priority = component_config.get('priority', 0)

src/lib/python/isc/bind10/sockcreator.py

@@ -20,10 +20,10 @@ import errno
 import copy
 import subprocess
 import copy
-from isc.log_messages.bind10_messages import *
+from isc.log_messages.init_messages import *
 from libutil_io_python import recv_fd
 
-logger = isc.log.Logger("boss")
+logger = isc.log.Logger("init")
 
 """
 Module that comunicates with the privileged socket creator (b10-sockcreator).
@@ -251,7 +251,7 @@ class Creator(Parser):
         """Function used before running a program that needs to run as a
         different user."""
         # Put us into a separate process group so we don't get
-        # SIGINT signals on Ctrl-C (the boss will shut everthing down by
+        # SIGINT signals on Ctrl-C (b10-init will shut everthing down by
         # other means).
         os.setpgrp()
 

src/lib/python/isc/bind10/socket_cache.py

@@ -106,7 +106,8 @@ class Cache:
     This is the cache for sockets from socket creator. The purpose of cache
     is to hold the sockets that were requested, until they are no longer
     needed. One reason is, the socket is created before it is sent over the
-    unix domain socket in boss, so we need to keep it somewhere for a while.
+    unix domain socket in b10-init, so we need to keep it somewhere for a
+    while.
 
     The other reason is, a single socket might be requested multiple times.
     So we keep it here in case someone else might ask for it.
@@ -175,7 +176,7 @@ class Cache:
           restrictions and of all copies of socket handed out are considered,
           so it can be raised even if you call it with share_mode 'ANY').
         - isc.bind10.sockcreator.CreatorError: fatal creator errors are
-          propagated. Thay should cause the boss to exit if ever encountered.
+          propagated. Thay should cause b10-init to exit if ever encountered.
 
         Note that it isn't guaranteed the tokens would be unique and they
         should be used as an opaque handle only.
@@ -220,11 +221,11 @@ class Cache:
         one returned from previous call from get_token. The token can be used
         only once to receive the socket.
 
-        The application is a token representing the application that requested
-        it. Currently, boss uses the file descriptor of connection from the
-        application, but anything which can be a key in a dict is OK from the
-        cache's point of view. You just need to use the same thing in
-        drop_application.
+        The application is a token representing the application that
+        requested it. Currently, b10-init uses the file descriptor of
+        connection from the application, but anything which can be a key in
+        a dict is OK from the cache's point of view. You just need to use
+        the same thing in drop_application.
 
         In case the token is considered invalid (it doesn't come from the
         get_token, it was already used, the socket wasn't picked up soon

src/lib/python/isc/bind10/special_component.py

@@ -26,23 +26,23 @@ class SockCreator(BaseComponent):
 
     Note: _creator shouldn't be reset explicitly once created.  The
     underlying Popen object would then wait() the child process internally,
-    which breaks the assumption of the boss, who is expecting to see
+    which breaks the assumption of b10-init, who is expecting to see
     the process die in waitpid().
     """
-    def __init__(self, process, boss, kind, address=None, params=None):
-        BaseComponent.__init__(self, boss, kind)
+    def __init__(self, process, b10_init, kind, address=None, params=None):
+        BaseComponent.__init__(self, b10_init, kind)
         self.__creator = None
 
     def _start_internal(self):
-        self._boss.curproc = 'b10-sockcreator'
+        self._b10_init.curproc = 'b10-sockcreator'
         self.__creator = isc.bind10.sockcreator.Creator(LIBEXECPATH + ':' +
                                                         os.environ['PATH'])
-        self._boss.register_process(self.pid(), self)
-        self._boss.set_creator(self.__creator)
-        self._boss.log_started(self.pid())
+        self._b10_init.register_process(self.pid(), self)
+        self._b10_init.set_creator(self.__creator)
+        self._b10_init.log_started(self.pid())
 
         # We are now ready for switching user.
-        self._boss.change_user()
+        self._b10_init.change_user()
 
     def _stop_internal(self):
         self.__creator.terminate()
@@ -64,12 +64,12 @@ class SockCreator(BaseComponent):
 
 class Msgq(Component):
     """
-    The message queue. Starting is passed to boss, stopping is not supported
-    and we leave the boss kill it by signal.
+    The message queue. Starting is passed to b10-init, stopping is not
+    supported and we leave b10-init kill it by signal.
     """
-    def __init__(self, process, boss, kind, address=None, params=None):
-        Component.__init__(self, process, boss, kind, None, None,
-                           boss.start_msgq)
+    def __init__(self, process, b10_init, kind, address=None, params=None):
+        Component.__init__(self, process, b10_init, kind, None, None,
+                           b10_init.start_msgq)
 
     def _stop_internal(self):
         """
@@ -78,7 +78,7 @@ class Msgq(Component):
         But as it is stateless, it's OK to kill it.
 
         So we disable this method (as the only time it could be called is
-        during shutdown) and wait for the boss to kill it in the next shutdown
+        during shutdown) and wait for b10-init to kill it in the next shutdown
         step.
 
         This actually breaks the recommendation at Component we shouldn't
@@ -89,24 +89,24 @@ class Msgq(Component):
         pass
 
 class CfgMgr(Component):
-    def __init__(self, process, boss, kind, address=None, params=None):
-        Component.__init__(self, process, boss, kind, 'ConfigManager',
-                           None, boss.start_cfgmgr)
+    def __init__(self, process, b10_init, kind, address=None, params=None):
+        Component.__init__(self, process, b10_init, kind, 'ConfigManager',
+                           None, b10_init.start_cfgmgr)
 
 class Auth(Component):
-    def __init__(self, process, boss, kind, address=None, params=None):
-        Component.__init__(self, process, boss, kind, 'Auth', None,
-                           boss.start_auth)
+    def __init__(self, process, b10_init, kind, address=None, params=None):
+        Component.__init__(self, process, b10_init, kind, 'Auth', None,
+                           b10_init.start_auth)
 
 class Resolver(Component):
-    def __init__(self, process, boss, kind, address=None, params=None):
-        Component.__init__(self, process, boss, kind, 'Resolver', None,
-                           boss.start_resolver)
+    def __init__(self, process, b10_init, kind, address=None, params=None):
+        Component.__init__(self, process, b10_init, kind, 'Resolver', None,
+                           b10_init.start_resolver)
 
 class CmdCtl(Component):
-    def __init__(self, process, boss, kind, address=None, params=None):
-        Component.__init__(self, process, boss, kind, 'Cmdctl', None,
-                           boss.start_cmdctl)
+    def __init__(self, process, b10_init, kind, address=None, params=None):
+        Component.__init__(self, process, b10_init, kind, 'Cmdctl', None,
+                           b10_init.start_cmdctl)
 def get_specials():
     """
     List of specially started components. Each one should be the class than can

src/lib/python/isc/bind10/tests/component_test.py

@@ -70,7 +70,7 @@ class BossUtils:
         isc.bind10.component.time.time = lambda: tm + 30
 
     # Few functions that pretend to start something. Part of pretending of
-    # being boss.
+    # being b10-init.
     def start_msgq(self):
         pass
 
@@ -103,7 +103,7 @@ class ComponentTests(BossUtils, unittest.TestCase):
         self.__registered_processes = {}
         self.__stop_process_params = None
         self.__start_simple_params = None
-        # Pretending to be boss
+        # Pretending to be b10-init
         self.__change_user_called = False
 
     def change_user(self):
@@ -149,7 +149,7 @@ class ComponentTests(BossUtils, unittest.TestCase):
         its behaviour.
 
         The process used is some nonsense, as this isn't used in this
-        kind of tests and we pretend to be the boss.
+        kind of tests and we pretend to be the b10-init.
         """
         component = Component('No process', self, kind, 'homeless', [])
         component._start_internal = self.__start
@@ -176,7 +176,7 @@ class ComponentTests(BossUtils, unittest.TestCase):
         Test the correct data are stored inside the component.
         """
         component = self.__create_component('core')
-        self.assertEqual(self, component._boss)
+        self.assertEqual(self, component._b10_init)
         self.assertEqual("No process", component._process)
         self.assertEqual(None, component._start_func)
         self.assertEqual("homeless", component._address)
@@ -539,7 +539,7 @@ class ComponentTests(BossUtils, unittest.TestCase):
 
     def register_process(self, pid, process):
         """
-        Part of pretending to be a boss
+        Part of pretending to be a b10-init
         """
         self.__registered_processes[pid] = process
 
@@ -570,13 +570,13 @@ class ComponentTests(BossUtils, unittest.TestCase):
 
     def stop_process(self, process, address, pid):
         """
-        Part of pretending to be boss.
+        Part of pretending to be b10-init.
         """
         self.__stop_process_params = (process, address, pid)
 
     def start_simple(self, process):
         """
-        Part of pretending to be boss.
+        Part of pretending to be b10-init.
         """
         self.__start_simple_params = process
 
@@ -632,14 +632,14 @@ class ComponentTests(BossUtils, unittest.TestCase):
 
     def set_creator(self, creator):
         """
-        Part of faking being the boss. Check the creator (faked as well)
+        Part of faking being the b10-init. Check the creator (faked as well)
         is passed here.
         """
         self.assertTrue(isinstance(creator, self.FakeCreator))
 
     def log_started(self, pid):
         """
-        Part of faking the boss. Check the pid is the one of the fake creator.
+        Part of faking the b10-init. Check the pid is the one of the fake creator.
         """
         self.assertEqual(42, pid)
 
@@ -706,8 +706,8 @@ class FailComponent(BaseComponent):
     """
     A mock component that fails whenever it is started.
     """
-    def __init__(self, name, boss, kind, address=None, params=None):
-        BaseComponent.__init__(self, boss, kind)
+    def __init__(self, name, b10_init, kind, address=None, params=None):
+        BaseComponent.__init__(self, b10_init, kind)
 
     def _start_internal(self):
         raise TestError("test error")
@@ -755,11 +755,12 @@ class ConfiguratorTest(BossUtils, unittest.TestCase):
         self.__core_log = self.__core_log_create + self.__core_log_start
         self.__specials = { 'test': self.__component_test }
 
-    def __component_test(self, process, boss, kind, address=None, params=None):
+    def __component_test(self, process, b10_init, kind, address=None,
+                         params=None):
         """
         Create a test component. It will log events to us.
         """
-        self.assertEqual(self, boss)
+        self.assertEqual(self, b10_init)
         return TestComponent(self, process, kind, address, params)
 
     def test_init(self):

src/lib/python/isc/config/cfgmgr.py

@@ -232,10 +232,10 @@ class ConfigManager:
             # handler, so make it use defaults (and flush any buffered logs)
             ccsession.default_logconfig_handler({}, self.log_config_data)
 
-    def notify_boss(self):
+    def notify_b10_init(self):
         """Notifies the Boss module that the Config Manager is running"""
         # TODO: Use a real, broadcast notification here.
-        self.cc.group_sendmsg({"running": "ConfigManager"}, "Boss")
+        self.cc.group_sendmsg({"running": "ConfigManager"}, "Init")
 
     def set_module_spec(self, spec):
         """Adds a ModuleSpec"""

src/lib/python/isc/config/tests/cfgmgr_test.py

@@ -177,9 +177,9 @@ class TestConfigManager(unittest.TestCase):
         self.assertTrue(self.fake_session.has_subscription("Boss", "ConfigManager"))
         self.assertFalse(self.cm.running)
 
-    def test_notify_boss(self):
-        self.cm.notify_boss()
-        msg = self.fake_session.get_message("Boss", None)
+    def test_notify_b10_init(self):
+        self.cm.notify_b10_init()
+        msg = self.fake_session.get_message("Init", None)
         self.assertTrue(msg)
         # this one is actually wrong, but 'current status quo'
         self.assertEqual(msg, {"running": "ConfigManager"})

src/lib/python/isc/log_messages/Makefile.am

@@ -1,7 +1,7 @@
 SUBDIRS = work
 
 EXTRA_DIST = __init__.py
-EXTRA_DIST += bind10_messages.py
+EXTRA_DIST += init_messages.py
 EXTRA_DIST += cmdctl_messages.py
 EXTRA_DIST += ddns_messages.py
 EXTRA_DIST += stats_messages.py
@@ -20,7 +20,7 @@ EXTRA_DIST += dbutil_messages.py
 EXTRA_DIST += msgq_messages.py
 
 CLEANFILES = __init__.pyc
-CLEANFILES += bind10_messages.pyc
+CLEANFILES += init_messages.pyc
 CLEANFILES += cmdctl_messages.pyc
 CLEANFILES += ddns_messages.pyc
 CLEANFILES += stats_messages.pyc

src/lib/python/isc/log_messages/bind10_messages.py

@@ -1 +0,0 @@
-from work.bind10_messages import *

src/lib/python/isc/log_messages/init_messages.py

@@ -0,0 +1 @@
+from work.init_messages import *

src/lib/server_common/portconfig.cc

@@ -152,7 +152,7 @@ installListenAddresses(const AddressList& new_addresses,
         throw;
     } catch (const exception& e) {
         // Any other kind of exception is fatal. It might mean we are in
-        // inconsistent state with the boss/socket creator, so we abort
+        // inconsistent state with the b10-init/socket creator, so we abort
         // to make sure it doesn't last.
         LOG_FATAL(logger, SRVCOMM_EXCEPTION_ALLOC).arg(e.what());
         abort();

src/lib/server_common/portconfig.h

@@ -92,8 +92,9 @@ parseAddresses(isc::data::ConstElementPtr addresses,
 /// but removes all the sockets it listened on. One of the exceptions is
 /// propagated.
 ///
-/// The ports are requested from the socket creator through boss. Therefore
-/// you need to initialize the SocketRequestor before using this function.
+/// The ports are requested from the socket creator through b10-init.
+/// Therefore you need to initialize the SocketRequestor before using this
+/// function.
 ///
 /// \param new_addresses are the addresses you want to listen on.
 /// \param address_store is the place you store your current addresses. It is
@@ -107,7 +108,7 @@ parseAddresses(isc::data::ConstElementPtr addresses,
 ///
 /// \throw asiolink::IOError when initialization or closing of socket fails.
 /// \throw isc::server_common::SocketRequestor::Socket error when the
-///     boss/socket creator doesn't want to give us the socket.
+///     b10-init/socket creator doesn't want to give us the socket.
 /// \throw std::bad_alloc when allocation fails.
 /// \throw isc::InvalidOperation when the function is called and the
 ///     SocketRequestor isn't initialized yet.

src/lib/server_common/socket_request.cc

@@ -34,21 +34,21 @@ namespace server_common {
 namespace {
 SocketRequestor* requestor(NULL);
 
-// Before the boss process calls send_fd, it first sends this
+// Before the b10-init process calls send_fd, it first sends this
 // string to indicate success, followed by the file descriptor
 const std::string& CREATOR_SOCKET_OK() {
     static const std::string str("1\n");
     return (str);
 }
 
-// Before the boss process calls send_fd, it sends this
+// Before the b10-init process calls send_fd, it sends this
 // string to indicate failure. It will not send a file descriptor.
 const std::string& CREATOR_SOCKET_UNAVAILABLE() {
     static const std::string str("0\n");
     return (str);
 }
 
-// The name of the ccsession command to request a socket from boss
+// The name of the ccsession command to request a socket from b10-init
 // (the actual format of command and response are hardcoded in their
 // respective methods)
 const std::string& REQUEST_SOCKET_COMMAND() {
@@ -56,7 +56,7 @@ const std::string& REQUEST_SOCKET_COMMAND() {
     return (str);
 }
 
-// The name of the ccsession command to tell boss we no longer need
+// The name of the ccsession command to tell b10-init we no longer need
 // a socket (the actual format of command and response are hardcoded
 // in their respective methods)
 const std::string& RELEASE_SOCKET_COMMAND() {
@@ -69,7 +69,7 @@ const size_t SOCKET_ERROR_CODE = 2;
 const size_t SHARE_ERROR_CODE = 3;
 
 // A helper converter from numeric protocol ID to the corresponding string.
-// used both for generating a message for the boss process and for logging.
+// used both for generating a message for the b10-init process and for logging.
 inline const char*
 protocolString(SocketRequestor::Protocol protocol) {
     switch (protocol) {
@@ -211,7 +211,7 @@ createFdShareSocket(const std::string& path) {
 // \return the socket fd that has been read
 int
 getSocketFd(const std::string& token, int sock_pass_fd) {
-    // Tell the boss the socket token.
+    // Tell b10-init the socket token.
     const std::string token_data = token + "\n";
     if (!isc::util::io::write_data(sock_pass_fd, token_data.c_str(),
                                    token_data.size())) {
@@ -226,7 +226,7 @@ getSocketFd(const std::string& token, int sock_pass_fd) {
         isc_throw(SocketRequestor::SocketError,
                   "Error reading status code while requesting socket");
     }
-    // Actual status value hardcoded by boss atm.
+    // Actual status value hardcoded by b10-init atm.
     if (CREATOR_SOCKET_UNAVAILABLE() == status) {
         isc_throw(SocketRequestor::SocketError,
                   "CREATOR_SOCKET_UNAVAILABLE returned");
@@ -258,7 +258,7 @@ getSocketFd(const std::string& token, int sock_pass_fd) {
 }
 
 // This implementation class for SocketRequestor uses
-// a CC session for communication with the boss process,
+// a CC session for communication with the b10-init process,
 // and fd_share to read out the socket(s).
 // Since we only use a reference to the session, it must never
 // be closed during the lifetime of this class
@@ -300,10 +300,10 @@ public:
                                        share_name.empty() ? app_name_ :
                                        share_name);
 
-        // Send it to boss
+        // Send it to b10-init
         const int seq = session_.group_sendmsg(request_msg, "Boss");
 
-        // Get the answer from the boss.
+        // Get the answer from b10-init.
         // Just do a blocking read, we can't really do much anyway
         isc::data::ConstElementPtr env, recv_msg;
         if (!session_.group_recvmsg(env, recv_msg, false, seq)) {
@@ -330,12 +330,12 @@ public:
         const isc::data::ConstElementPtr release_msg =
             createReleaseSocketMessage(token);
 
-        // Send it to boss
+        // Send it to b10-init
         const int seq = session_.group_sendmsg(release_msg, "Boss");
         LOG_DEBUG(logger, DBGLVL_TRACE_DETAIL, SOCKETREQUESTOR_RELEASESOCKET).
             arg(token);
 
-        // Get the answer from the boss.
+        // Get the answer from b10-init.
         // Just do a blocking read, we can't really do much anyway
         isc::data::ConstElementPtr env, recv_msg;
         if (!session_.group_recvmsg(env, recv_msg, false, seq)) {

src/lib/server_common/tests/portconfig_unittest.cc

@@ -330,8 +330,8 @@ TEST_F(InstallListenAddressesDeathTest, inconsistent) {
     }
 }
 
-// If we are unable to tell the boss we closed a socket, we abort, as we are
-// not consistent with the boss most probably.
+// If we are unable to tell the b10-init we closed a socket, we abort, as we
+// are not consistent with b10-init most probably.
 TEST_F(InstallListenAddressesDeathTest, cantClose) {
     if (!isc::util::unittests::runningOnValgrind()) {
         installListenAddresses(valid_, store_, dnss_);

tests/lettuce/features/terrain/bind10_control.py

@@ -204,7 +204,7 @@ def parse_bindctl_output_as_data_structure():
 def find_process_pid(step, process_name):
     """Helper function to request the running processes from Boss, and
        return the pid of the process with the given process_name.
-       Fails with an assert if the response from boss is not valid JSON,
+       Fails with an assert if the response from b10-init is not valid JSON,
        or if the process with the given name is not found.
     """
     # show_processes output is a list of lists, where the inner lists