Re: Unbound chroot via rc difficulties getting started

[qab smith <qabulin%gmail.com@localhost>]

Yeah, I’m noticing a symlink, as well as the check for it in the unbound rc
script’s precmd function and the check if unbound_chrootdir is set.  The
question about how Unbound is starting and dropping into chroot seems less
about how NetBSD rc handles process start with precmd, and my confusion is
more specific to Unbound.  I’ll chock it up to working as intended per the
third party application.
Thanks for the reply!


From: Chavdar Ivanov <ci4ic4%gmail.com@localhost> <ci4ic4%gmail.com@localhost>
Date: September 24, 2018 at 03:46:04
To: qabulin%gmail.com@localhost <qabulin%gmail.com@localhost> <qabulin%gmail.com@localhost>
CC: netbsd-users @ netbsd. org <netbsd-users%netbsd.org@localhost>
<netbsd-users%netbsd.org@localhost>
Subject:  Re: Unbound chroot via rc difficulties getting started

I have one RPI model B, running 8.99.2, which has been running my home
> DNS server since, well, 8.99.2 (it had some 10 months uptime until the
> fuse tripped for some reason)... I don't remember doing anything
> special to make is start chrooted (there was already
> "unbound_chrootdir=/var/chroot/unbound" in /etc/defaults/rc.conf),
> except creating the link "cd /etc; ln -s
> /var/chroot/unbound/etc/unbound unbound" after the unbound_migrate was
> ran.
> On Mon, 24 Sep 2018 at 08:00, qab smith <qabulin%gmail.com@localhost> wrote:
>
>
> Unbound initially was not able to start for me in chroot using rc scripts