Re: pkgsrc bind9 still trying to run base bind

[Mark Cullen <mark.r.cullen@xxxxxxxxx>]

Mark Cullen wrote:
> Petr Janda wrote:
>
> > try putting this in your rc.conf:
> >
> > named_enabled = NONE
> > named = YES
> >
> > First one should disable base bind, second one should enable PKGSRC's 
> > bind.
> >
> > By the way guys, wouldnt it be a good idea to sync BIND to the current 
> > version?
>
>
> Nope, that aint it either. I think maybe the script is broken or something?
>
> Tried named_enabled="NONE" and named="YES", still trying to run the base 
> bind. Tried named_enabled="NONE" and named9="YES", same. Tried 
> named_enabled="NO" and named9="YES"...... same :-(

I edited the script very slightly and got it to start 9.3.1.

---

#!/bin/sh
#
# $NetBSD: named9.sh,v 1.3 2005/05/17 13:17:34 sketch Exp $
#

# PROVIDE: named
# REQUIRE: SERVERS
# BEFORE:  DAEMON
# KEYWORD: chrootdir

.  /etc/rc.subr

#name="named"
#rcvar="${name}9"
#command="/usr/pkg/sbin/${name}"

name="named9"
rcvar="named9"
command="/usr/pkg/sbin/named"

[...snip...]

---

/var/log/messages:
Apr 27 19:54:36 df named[1124]: starting BIND 9.3.1 -u named -t /etc/namedb
Apr 27 19:54:36 df named[1124]: none:0: open: /etc/named.conf: file not 
found
Apr 27 19:54:36 df named[1124]: loading configuration: file not found
Apr 27 19:54:36 df named[1124]: exiting (due to fatal error)

The actual line that causes it is the name="named" line. If I change 
this to name="named" it'll go back to trying to run the base bind. No 
idea why it's looking for /etc/named.conf instead of 
/etc/namedb/named.conf though. Adding named9_flags="-c named.conf" to 
/etc/rc.conf seems to make it look back in /etc/namedb/named.conf. I'd 
have really have thought it would have defaulted there though.