BIND 10 #1147: Boss should give up after n unsuccessful attempts to start a module

[BIND 10 Development]

#1147: Boss should give up after n unsuccessful attempts to start a module
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  minor         |                    Milestone:  New
           Component:  Boss of BIND  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 If a module has a fatal problem and can not be started (eg. it crashes
 right after being started), boss keeps restarting it and is „jumping“.
 This isn't a serious problem, but it eats resources unnecessarily and is
 annoying, because it fills logs. This sometimes leads to workarounds like
 the one in #1146.

 I suggest that if the started process dies in 10s from being started, we
 count it as an unsuccessful attempt to start it. If we do 5 of them in a
 row (without a successful one), we give up more attempts to start it,
 since it's hopeless (for some value of 10 and 5).

 Then we would add a command an admin could use to ask boss to try again
 (after the admin thinks the problem was fixed) ‒ reset the count of
 unsuccessful attempts to 0 again.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1147>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development