Date: Wed, 24 Apr 2013 18:55:42 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: sbruno@freebsd.org Cc: current@freebsd.org Subject: Re: 'service named reload' with non-default system directories. Message-ID: <E1UV2yt-0006YV-34@clue.co.za> In-Reply-To: <1366820838.1405.3.camel@localhost> References: <1366820838.1405.3.camel@localhost> <E1UV0nX-0006S1-QK@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1UV2yt-0006YV-34>