Joe Abley via Unbound-users writes:
>
> On Jan 1, 2021, at 14:15, Gil Levy via Unbound-users
> <unbound-users@lists.nlnetlabs.nl> wrote:
>
> >> Are you running unbound in a chroot(8)?
> > I don't know how to check that.
>
> man chroot
>
> for a better description of what chroot does, and how the interpretation of
> absolute pathnames differs inside and outside the chroot namespace.
>
> man man
>
> if you're unfamiliar with how manual pages are organised. If you don't have
> manual pages installed and can't add them as a package, it should not be hard
> to find collections of manual pages for your particular distribution if you
> search for them.
>
> grep chroot unbound.conf
For a running unbound, do
unbound-control get_option chroot
to get the value it is using.
> seems like a reasonable place to start to find configuration options in your
> environment that relate to chroot. You might also refer to the unbound
> documentation to understand the defaults and the specific meaning of
> individual
> parameters.
Especially take notice what
man unbound.conf
tells you about the interaction between chroot and absolute path names.
>
> Another common error is to try and write log files to places where the
> process
> generating them does not have the necessary permissions. Determine the
> user that unbound is running as and check the permissions in the filesystem.
Or the directories are missing after the chroot took place...
jaap
