BIND 10 #3021: bad configuration caused cc timeout and tracebacks

[BIND 10 Development]

#3021: bad configuration caused cc timeout and tracebacks
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  Unclassified  |  Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by vorner):

 Well, I think it would be easier to try reading the CC non-blocking more
 than once (with shorter timeouts, or with select) and also check if the
 started process exited. It would be easier.

 Or we could just make sure we terminate correctly when the timeout
 happens.

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