BIND 10 #1543: the socket requestor should abort itself on unexpected errors

[BIND 10 Development]

#1543: the socket requestor should abort itself on unexpected errors
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  jinmei                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20120207
                   Priority:         |            Resolution:
  blocker                            |             Sensitive:  0
                  Component:  Boss   |           Sub-Project:  DNS
  of BIND                            |  Estimated Difficulty:  3
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
  Socket creator                     |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => UnAssigned
 * status:  accepted => reviewing


Comment:

 Hello

 It should be ready for review. It is based on the #1542 branch, which is
 still in review, because I use the exceptions introduced there to
 recognize the OK to continue error cases. The first commit there
 (058f2664b387c531920c6068b29cee34fc966a05) is just trivial merge with
 master, to keep up to date.

 I think this might need a changelog entry, as it changes the user visible
 behaviour:
 {{{
 [feature]       vorner
 When the allocation of a socket fails for a different reason than the
 socket
 not being provided by the OS, the b10-auth and b10-resolver abort, as the
 system might be in inconsistent state after such error.
 }}}

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