Thanks, that did the trick. I'm not running this in a jail because I'm paranoid or anything -- I just need a test environment, and I don't have an extra machine kicking around. :)
Patrick On 5/1/06, David Robillard <[EMAIL PROTECTED]> wrote:
BIND is trying to setup a chroot(8) before it starts. If you're already inside a jail, then IMHO it is a little overkill (i.e. Running BIND in a chroot inside a jail). Check the BIND related values in rc.conf(5). The chroot(8) startup is triggered via this one: named_chrootdir="/var/named" # Chroot directory (or "" not to auto-chroot it) So try setting it to named_chrootdir="" and it should disable the chroot code from the startup script. Of course, if you still need to chroot(8) your named(8) install inside your jail, then you're at the same point. Consider running another jail perhaps? Or use BIND's view feature. Hope this helps, David > Thanks, > > Patrick > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > [EMAIL PROTECTED]" -- David Robillard UNIX systems administrator, CISSP Montreal: +1 514 966 0122
_______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
