On Thu, Jul 27, 2017 at 06:47:38PM +0200, Emeric Brun wrote: > A second point, i don't know which is the current policy about the keyword > prefix "no-" in configuration statements, but > we usually take care using this word. > > Willy, would you clarify that point?
In fact we were very careful to avoid them for the "server" lines to limit the trouble in prevision for the server-template directive and the "no-whatever" that came with it. Other than that we already have a few "no-" on bind lines, and I think that when they disable part of a feature that is on by default due to another option it makes sense as there's little confusion. Willy
