Thanks, Andre
I reverted my change to rc.subr
I tried what you suggested and it seemed to work,
(believe it or not,
I tried somehting similar this morning but i must have had typo in my
syntax)
Thanks Tom Smyth
On Thu, 25 Oct 2018 at 13:53, Andre Stoebe wrote:
>
> Use "rcctl set unbound timeout
Use "rcctl set unbound timeout 300", which sets "unbound_timeout=300" in
rc.conf.local. The variables are documented in rc.d(8).
Regards
André
Hello,
to resolve the rcctl start unbound timeout issue,
I tried increasing daemon_timeout value in multiple files (and failing)
finally i edited line 300 of /etc/rc.d/rc.subr
- [ -z "${daemon_timeout}" ] && daemon_timeout=30
+ [ -z "${daemon_timeout}" ] && daemon_timeout=300
Hi Predrag,
Thanks for taking a look,
im running
OpenBSD fns1.ogmaconnect.com 6.4 GENERIC.MP#364 amd64
It would appear that the killed message was due to insufficient memory on
the
machine,
However the issue with rcctl start unbound still remains despite the
increase
of the ram on the vm
ok so
Tom Smyth wrote:
> Hello all,
> unbound-checkconf "Killed" when cheking a large local zone config file
> rcctl start unbound fails because of the above command failing
>
> background
>
> we were migrating our dns filtering from one platform to openbsd
> so we have a basic unbound configuration
Hello all,
unbound-checkconf "Killed" when cheking a large local zone config file
rcctl start unbound fails because of the above command failing
background
we were migrating our dns filtering from one platform to openbsd
so we have a basic unbound configuration file that loads another
6 matches
Mail list logo
