RELENG_7 changes for rc.d/named

[Oliver Lehmann]

Hi,

since my last RELENG_7 update a new rc.conf variable named_conf appeared.

How is this supposted to work with a chroot named? I guess not at all?

I have in my rc.conf:

named_enable="YES"
named_program="/usr/local/sbin/named"
named_flags="-u bind -c /etc/named/named.conf"
named_chrootdir="/usr/chroot/named"
named_symlink_enable="YES"
named_conf="/usr/chroot/named/etc/named/named.conf"
#named_conf="/etc/named/named.conf"

When I now try to start named:

# /etc/rc.d/named start
/usr/chroot/named/etc/named/named.conf:12: change directory to '/etc/named' failed: file not found

/usr/chroot/named/etc/named/named.conf:12: parsing failed
/etc/rc.d/named: ERROR: named-checkconf for $named_conf failed
Exit 3
#

Of cource /etc/named does not exists because when the configuration file
is used, /etc/named is for named in reality /usr/chroot/named/etc/named...

To illustrate how it is implemented and how it would work if it gets right:

# named-checkconf /usr/chroot/named/etc/named/named.conf
/usr/chroot/named/etc/named/named.conf:12: change directory to '/etc/named' failed: file not found

/usr/chroot/named/etc/named/named.conf:12: parsing failed
Exit 1
# named-checkconf -t /usr/chroot/named /etc/named/named.conf
# 

Could this please be fixed so it works with a chrooted named too?
I now have to change the rc.d file on my own to get named to startup
(Luky me I added backup resolvers in resolv.conf before I rebooted the system)

-- 
 Oliver Lehmann
  http://www.pofo.de/
  http://wishlist.ans-netz.de/