BIND 10 #2072: b10-ddns and Broken pipe on component removal

BIND 10 Development do-not-reply at isc.org
Mon Jun 25 13:08:08 UTC 2012


#2072: b10-ddns and Broken pipe on component removal
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 b10-ddns can be enabled to be started even though its dependencies are not
 enabled. So it will start and stop continually. So when stopping  it, it
 may not be running:

 {{{
 > config remove Boss/components b10-ddns
 > config commit
 Error: [Errno 32] Broken pipe
 Configuration not committed
 }}}

 I think this was caused by: boss asking it to shut down, but it already
 was not running due to no zonemgr, and timed just right since hadn't re-
 started again.

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


More information about the bind10-tickets mailing list