BIND 10 #642: SIGHUP and other signals cause boss to leave BIND 10 processes lying around

[BIND 10 Development]

#642: SIGHUP and other signals cause boss to leave BIND 10 processes lying around
-------------------------------------+-------------------------------------
                 Reporter:  shane    |                Owner:  shane
                     Type:  defect   |               Status:  new
                 Priority:  minor    |            Milestone:  A-Team-Task-
                Component:  Boss of  |  Backlog
  BIND                               |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------

Comment (by shane):

 Okay, this has been done and is ready for review in branch trac642.

 It involved a bit of refactoring of the code to allow tests to be written
 for this. The main thing was splitting the main() function up into
 separate functions. This allows the setup code to be run without actually
 starting the server. This is useful for testing the signal handling code,
 since we can then have signal handlers installed but not actually run the
 main loop.

 I did have to poke around a bit inside the bind10 module itself, in order
 to use the "mock" boss class instead of the real one. This insures we
 don't actually start all of the programs when we begin.

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