BIND 10 #420: Unresponsive process can block msgq

[BIND 10 Development]

#420: Unresponsive process can block msgq
-------------------------------------+-------------------------------------
                 Reporter:  shane    |                Owner:  zzchen_pku
                     Type:  defect   |               Status:  reviewing
                 Priority:  major    |            Milestone:  A-Team-
                Component:  msgq     |  Sprint-20110126
                 Keywords:           |           Resolution:
Estimated Number of Hours:  13.0     |            Sensitive:  0
                Billable?:  1        |  Add Hours to Ticket:  0
                Internal?:  0        |          Total Hours:  0.5
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => zzchen_pku


Comment:

 I changed the parameter to bool and added check that the data returned
 from MsgQ are the ones expected, so if anything is changed/lost/added
 somewhere should be detected. It is in the last two commits.

 But what is the concern about fork or sendall throwing exception? The
 exceptions mean either a bug (the remote side of sendall is no longer
 there) or reaching some OS limit. In both cases, the test would fail
 (either by the exception itself or the sub-process dieing), which isn't a
 problem in the rare occasion of broken system. If it wasn't test, it would
 make sense to catch them and change them to a better error message, but is
 it really needed in test? Or do you see some bigger problem there than the
 test would simply fail or crash?

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