bin/73929: /etc/rc.d/named will not work with ports-named

[Oliver Lehmann]

>Number:         73929
>Category:       bin
>Synopsis:       /etc/rc.d/named will not work with ports-named
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 14 10:30:27 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Oliver Lehmann
>Release:        FreeBSD 4.10-STABLE i386
>Organization:
>Environment:
System: FreeBSD kartoffel.salatschuessel.net 4.10-STABLE FreeBSD 4.10-STABLE #0: Fri Jun 4 20:32:48 CEST 2004 olivleh1 at kartoffel.salatschuessel.net:/usr/obj/usr/src/sys/KARTOFFEL i386


	FreeBSD avocado.salatschuessel.net 5.3-STABLE FreeBSD 5.3-STABLE #1: Sat Nov 13 15:16:49 CET 2004     olivleh1 at avocado.salatschuessel.net:/usr/obj/usr/src/sys/AVOCADO  i386

>Description:
	/etc/rc.d/named tries to run rndc-confgen if "${named_chrootdir}/etc/namedb/rndc.key" and "${named_chrootdir}/etc/namedb/rndc.conf"
	is nonexistent.
	a) rndc-confgen installed from dns/bind93 only generates /usr/local/etc/rndc.key and
	   ${confgen_chroot}/usr/local/etc/rndc.key so rndc-confgen will be run everytime
	   /etc/rc.d/named is called.
	b) /usr/local/sbin isn't in PATH at bootup - calling "rndc-confgen" at bootup will
	   fail. That will cause named to not startup.

>How-To-Repeat:
	remove base-bind, install bind from ports, run /etc/rc.d/named and/or reboot
>Fix:

        PREFIX=${named_program%%/sbin/named}

	if [ "${PREFIX}"  = "/usr" -a ! -f "${named_chrootdir}/etc/namedb/rndc.key" -a ! -f "${named_chrootdir}/etc/namedb/rndc.conf" ] || \
	   [ "${PREFIX}" != "/usr" -a ! -f "${named_chrootdir}/${PREFIX}/etc/rndc.key" ] ; then
		${PREFIX}/sbin/rndc-confgen -a -b256 ${confgen_chroot}
	fi

>Release-Note:
>Audit-Trail:
>Unformatted: