BIND 10 #2455: bind10 parent should not exit if b10-auth exits with fatal

[BIND 10 Development]

#2455: bind10 parent should not exit if b10-auth exits with fatal
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  New Tasks
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  Boss   |           Sub-Project:  Core
  of BIND                            |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jreed):

 Replying to [comment:2 jinmei]:
 > I don't fully understand the "execute" magic, but isn't it the
 > expected behavior that the bind10 process dies if a "needed" component
 > fails to start?  Or are you suggesting we should change this behavior?


 kind is set to "needed".

 The guide documentation says: ``If it is set to “needed” and it fails at
 startup, the whole bind10 shuts down and exits with an error exit code.
 But if it fails some time later, it is just started again. If you set it
 to “core”, you indicate that the system is not usable without the
 component and if such component fails, the system shuts down no matter
 when the failure happened.''

 In my case, the system already was started and running (that is how I had
 access to cmdctl and cfgmgr).  To shutdown after startup, it would set
 kind to "core".

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