> Yes, pointing at a different config file breaks the startup checks.
That is the primary reason I submitted the bug report.
> With two instances, I'm not sure we want to cater for such setups.
> Are two instances really needed or is this a special snowflake?
I need a forwarder for "." and no forwarding for a subdomain.
Unbound does not allow this in one instance, not that I can find.
Why? Quad9 for malicious site filtering and spamhaus for RBL.
> getopts with a leading : reads much nicer than spamlogd's sed(1) golf,
> but it still looks like... too much.
I could have just used "${daemon_flags##* }" and been done with it.
I figured using getopts was more the "correct" way to parse
daemon_flags. What if "-d -c /path/to/unbound.conf -v" was used?
My patch would still extract the configuration filename properly.
> i much prefer the expanded version rather than this one-liner which
> relies on "For historical reasons, open and close braces may be used
> instead of in and esac"
Right after hitting send I realized the compact formatting would
be questioned. So I quickly corrected for that in a follow-up.
I followed the example in "man ksh" for getopts.
> + while getopts :l: _opt $daemon_flags; do
> + [[ $_opt == l ]] && pflog=$OPTARG
> + done
You are the experts but (to me) this looks like assumptions are still
being made about the formatting of what's in daemon_flags.
