BIND 10 #1443: allow bind10 to run even if configuration is corrupted

[BIND 10 Development]

#1443: allow bind10 to run even if configuration is corrupted
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:  jelte
                       Type:         |                Status:  reviewing
  defect                             |             Milestone:
                   Priority:         |  Sprint-20120403
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  configuration                      |           Sub-Project:  Core
                   Keywords:         |  Estimated Difficulty:  4
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => jelte


Comment:

 This looks good to go in now.

 Btw, you may want to handle the case where the backup file already
 exists.. I mean the cause for something like:

 {{{
          if new_file_name is None:
              new_file_name = old_file_name + ".bak"
 +        if os.path.exists(new_file_name):
 +            i = 1
 +            while os.path.exists(new_file_name + "." + str(i)):
 +                i = i + 1
 +            new_file_name = new_file_name + "." + str(i)
          if os.path.exists(old_file_name):
              logger.info(CFGMGR_RENAMED_CONFIG_FILE, old_file_name,
 new_file_name)
              os.rename(old_file_name, new_file_name)
 }}}

 But maybe that's overkill. :)

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