Sean Bruno wrote:
> Would we need a change to /etc/defaults/rc.conf to set ${named_confdir}
> to the default location if not set?
I'm not sure. It's derived:
load_rc_config $name
# Updating the following variables requires that rc.conf be loaded first
#
required_dirs="$named_chrootdir" # if it is set, it must exist
named_confdir="${named_chrootdir}${named_conf%/*}"
I don't think that I did a particularly good job of making it work
for all instances. It's more of an opening move to get this working
properly wherever the admin chooses to put the named chroot. I'm
still expecting comments from Doug Barton.
> Also, there already appears to be a ${named_conf} that points to
> whatever named.conf specified (defaults to /etc/namedb/named.conf). Is
> this complementary to what you're poking at?
This is specifically rndc (not named) that fails to find its key
or config if you choose to use a chrootdir that isn't the default.
Ian
--
Ian Freislich
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
