hi, I’m just looking through the rc.d scripts in contrib/ in the source package, and I’m just wondering: why copy over /etc/resolv.conf into the chroot? Surely unbound doesn’t actually rely on that to do anything?
Doing a quick test also seems to show that unbound still works without resolv.conf in the chroot.
-jf
Hello, anybody?
-jf
hey,
Hello, anybody?
We run all our resolvers without resolv.conf in the chroot, no issues.
Looking at debian init scripts, they also only copy /etc/unbound over to chroot.
thanks, Thomas and Tarko. I appreciate the answers.
@Thomas: running unbound with resolv.conf in the chroot seems to work just
fine, hence my question. I'm not so concerned about the difference as I am
about whether unbound works or not. And as my own experience has been,
unbound works without resolv.conf.
@Tarko: that's certainly surprising. Can you check whether the chroot has
/dev/random or /dev/urandom?
thanks,
-jf
hey,
@Tarko: that's certainly surprising. Can you check whether the chroot
has /dev/random or /dev/urandom?
Of course it has /dev/random (it also has /dev/null), I was only speaking about configs in /etc.
Init script doesn't take care of it, I think I mknoded them manually when setting up the chroot.