Hmmm... I only have a couple of free minutes here, but I
skimmed through this.
I think that named_rcng is simply mis-named. It's used twice
in /etc/rc.d/named. The second looks bogus; I'm pretty sure
it (and the entire case statement around it) can safely
be deleted.
Regardless of how named_rcng is set, /etc/rc.d/named will
still start named. (This is why I say it's mis-named;
Christian seems to have misunderstood it to determine whether
or not /etc/rc.d/named would start named.) The difference
is simply which set of variables get used:
named_rcng = NO
named_flags is obeyed
named_chrootdir, named_chroot_autoupdate, and named_symlink_enable
are not obeyed.
named_rcng = YES
named_flags is not obeyed; it gets overwritten with auto-generated
flags
named_chrootdir, named_chroot_autoupdate, and named_symlink_enable
are obeyed.
Forcing it YES certainly has the potential of breaking some
existing installations because it ignores named_flags.
If we're going to do it, do it before 5.2. However, I would
suggest changing the code so that named_flags gets obeyed if
it is set. In that case, we could dump named_rcng, set
named_flags="" in /etc/defaults/rc.conf and just possibly
manage to avoid breaking anything.
Like I said, this is all based on a pretty cursory study;
I might be mis-reading something.
In any case, the comments in /etc/defaults/rc.conf should be
augmented to make it clear which variables are obeyed for
each setting of named_rcng.
Tim
Gordon Tetlow wrote:
> Forwarded to the rc mailing list. Tim, do you want to weigh in on this?
>
> IIRC, it has something to do with the way NetBSD does named startup
> (which is in a chroot?) while we do it the old fashioned simpler way.
>
> -gordon
>
> ----- Forwarded message from Christian Weisgerber <naddy@...> -----
>
> Date: Sun, 7 Sep 2003 13:28:42 +0200
> From: Christian Weisgerber <naddy@...>
> To: gordon@...
> Subject: -CURRENT rc_ng: named_rcng
> X-Spam-Status: No, hits=-7.5 required=6.5
> tests=BAYES_10,USER_AGENT_MUTT
> autolearn=ham version=2.55
>
> Shouldn't named_rcng default to "YES" now or in fact be completely
> removed, considering that no alternative startup exists any longer?
>