BIND 10 #1818: change default boss config to not run b10-auth

[BIND 10 Development]

#1818: change default boss config to not run b10-auth
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:  muks
                       Type:  task   |                Status:  reviewing
                   Priority:         |             Milestone:
  medium                             |  Sprint-20120417
                  Component:  Boss   |            Resolution:
  of BIND                            |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  1
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by muks):

 Up for review again. I have addressed the issues to do with components not
 starting up, or not shutting down before a test is run.

 There still seem to be some issues reported on a Mac OS X box:
 {{{
 2012-04-11 06:19:11.401 ERROR [b10-auth.cc] CC_ASYNC_READ_FAILED
 asynchronous read failed
 2012-04-11 06:19:11.402 FATAL [b10-auth.auth] AUTH_SERVER_FAILED server
 failed: asynchronous read failed
 2012-04-11 06:19:11.405 INFO  [b10-boss.boss] BIND10_LOST_SOCKET_CONSUMER
 consumer 17 of sockets disconnected, considering all its sockets closed
 2012-04-11 06:19:11.406 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 15511 of b10-auth ended with status 256
 2012-04-11 06:19:11.406 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
 component b10-auth (pid 15511) failed: process exited normally with exit
 status 256
 2012-04-11 06:19:11.406 FATAL [b10-boss.boss] BIND10_COMPONENT_UNSATISFIED
 component b10-auth is required to run and failed
 2012-04-11 06:19:11.406 INFO  [b10-boss.boss] BIND10_SHUTDOWN stopping the
 server
 2012-04-11 06:19:11.406 INFO  [b10-boss.boss] BIND10_CONFIGURATOR_STOP
 bind10 component configurator is shutting down
 2012-04-11 06:19:11.407 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component Socket creator is being stopped
 2012-04-11 06:19:11.407 INFO  [b10-boss.boss] BIND10_SOCKCREATOR_TERMINATE
 terminating socket creator
 2012-04-11 06:19:11.407 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component msgq is being stopped
 2012-04-11 06:19:11.407 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-cmdctl is being stopped
 2012-04-11 06:19:11.407 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-cmdctl to shut down
 2012-04-11 06:19:11.407 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component cfgmgr is being stopped
 2012-04-11 06:19:11.407 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 cfgmgr to shut down
 2012-04-11 06:19:12.408 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 15510 of b10-cmdctl ended with status 0
 2012-04-11 06:19:12.408 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 15509 of cfgmgr ended with status 0
 2012-04-11 06:19:12.408 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 15492 of Socket creator ended with status 0
 2012-04-11 06:19:12.408 INFO  [b10-boss.boss] BIND10_SEND_SIGTERM sending
 SIGTERM to msgq (PID 15494)
 }}}

 But I don't think this has anything to do with the changes made in this
 branch. The testsuite passes on Linux. Jeremy is going to check it on a
 different OS.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1818#comment:16>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development