Some systems - only one that I am aware of, complain that unbound is starting before dchp6 has completed leading to problems, this occurs only on boot.
Further examination did indeed show that the problem is caused by unbound starting before the dhcp6c - RTSOLD - rc.newwanipv6 have completed, making sure that these have all run before unbound is allowed to start corrects the problem....
DOn't automatically update CIDR masks if the selector is disabled
Do not use reference to avoid losing data
Ignore upgrade_167_to_168() when upgrade_166_to_167() runs, they are both the same
Always run additional_config_upgrade() and do it after config is written
Each item in additional_config_upgrade() must write config after changing it
Detect old workarounds in config upgrade and deal with them
Bring upgrade_166_to_167() to 2.3 world
Move workaround used to enable pkg metadata update cronjob to a generic mechanism
Check if specific config upgrade code already ran and skip it
View revisions
Also available in: Atom