0 on success (or upgrade aborted by user)
1 on check and need update
2 on check and version of db too high
3 on command-line error
4 on db read error
5 on upgrade error
- s/NSEC3PARAMETER/NSEC3PARAM/
- "definitely" is too strong in this context
- add a space after a comma
- "zonefile" is awkward (there's no "zonefile" in this context)
- "NSEC3 method" is an awkward term
- "this zone signature" is also awkward
in the previous version, if one is returned from find() and the other is
from getAdditional() they are not recognized as of the same kind, because
the underlying pointers are different.
The previous version crashes if the wildcard node is empty. Also, the
previous version didn't work well if there were multiple wildcard matches
because the auxiliary tree changes as we add more nodes and stored
pointer can become invalid. The fix to this issue is a bit complicated;
I needed to make the process two-stage.
This will prevent it from causing definition bloat even if the linkder
doesn't combine the constant def. It would also make more sense to make
it inaccessible from others anyway, because it's basically an
implementation-internal constatnt.
- if self.clear_config is None was wrong, should just be if self.clear_config
- 'back up' should have been 'create backup of'
- default value for unused parameter rename_config_file in b10-cfgmgr_test.py.in MyConfigManager should have been False, not None
- reordered message file
And remove the now renamed/removed internal only zone_new_data_ready
command.
Regenerate nroff file too (which includes
No new changelog entry. This goes with changelog entry 402.
Somewhat discussed on jabber. Didn't get consensus on one sentence,
but that can always be clarified later.
note: there's an error in the test description itself. In "7.2.2 other",
the result should be NOERROR, not NXDOMAIN, because it should match
*.w.example (BIND 9 indeed returns NOERROR, for that matter). I fixed
this, then all tests passed.
this could be slightly more efficient because it avoids redundant calls
to vector::end(). In my experiments I actually didn't see much difference,
but it doesn't harm anyway.
that way we don't have to expose mutable member variables of `Query`.
now the responsibility of the "inserter" is enlarged, also renamed it
to represent the new job more appropriately.
also avoid referring to an invalid range of iterator with operator+; use
end() instead (although the original code was probably safe at least in
practice).
