> If you think supporting multiple unbounds is sensible, then sure, > we should unify scripts as much as possible.
How about just for fixing rc_pre to do the right thing. Luckily rc_pre isn't critical and the second unbound will still start up ok on unpatched rc.d script even though rc_pre is looking at the wrong configuration file. There's no need to mention multiple unbounds, the bottom of "man rcctl" already nicely descibes running multiple daemons. (although it's suggesting absolute paths instead of realative paths) > Looks like this with local and our usual ksh style; yet untested, > I only run a single default unbound. I have been running two unbounds for awhile and only recently found a cleaner way of patching the unbound script that I thought to be worthy enough to submit a patch for. I had mentioned my reasons for wantting to run two unbounds, I know I'm in a tiny minority. Like any other daemon you just have to be sure you are not trying to use the same resources. I left out my unbound.conf because I consider it off-topic for this patch discussion but could do a write-up (on misc@) if there's enough interest for it. Thanks for looking at my patch and considering it.
