[bind10-dev] Updating configuration smoothly when options are removed

[JINMEI Tatuya / 神明達哉]

At Thu, 1 Mar 2012 10:52:27 +0100,
Michal 'vorner' Vaner <michal.vaner at nic.cz> wrote:

> When we upgrade the configuration by removing some options (like we do now with
> the outdated and no longer used logging configuration for Xfrout), a user that
> has it in the configuration has a problem, because when starting the new
> version, it will look at the spec of the configuration and reject it, because
> the configuration option is no longer valid. This will prevent the corresponding
> component to start, so it can't even be reconfigured. The user needs to shut
> everything down, open the configuration file in an editor and remove it
> manually. That is clearly a bad idea. I went for this in the case of Xfrout
> (because the configuration doesn't work for half a year already, we didn't have
> any users then, therefore the chance of somebody having the configuration there
> is low), but we need to solve it for future.

I agree we should make it more user friendly.  Right now I have no
idea about what's the best way to do that.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.