BIND 10 #1443: allow bind10 to run even if configuration is corrupted
BIND 10 Development
do-not-reply at isc.org
Mon Mar 19 16:53:19 UTC 2012
#1443: allow bind10 to run even if configuration is corrupted
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: | Status: new
defect | Milestone: Next-Sprint-
Priority: | Proposed
medium | Resolution:
Component: | Sensitive: 0
configuration | Sub-Project: Core
Keywords: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jelte):
hmm, not 100% sure, but didn't we used to do that and change it because
that would mean it is very easy to not notice it's not running the way it
should be? One change and you lose everything (granted, you may have
already lost everything depending on how corrupted it is).
I do think we should have a way to recover from corrupt config without
manual editing of the file, but not sure whether running by defaults would
be the correct approach there.
--
Ticket URL: <http://bind10.isc.org/ticket/1443#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list