Gelsema, P (Patrick) - FreeBSD wrote:
> In /etc/rc.conf I got the following.
> hulk# cat /etc/rc.conf | grep named
> named_enable="YES"
> named_uid="bind"
> named_chrootdir="/var/named"
grep named /etc/defaults/rc.conf
# named.  It may be possible to run named in a sandbox, man security for
named_enable="NO"               # Run named, the DNS server (or NO).
named_program="/usr/sbin/named" # path to named, if you want a different
#named_flags=""                 # Flags for named
named_pidfile="/var/run/named/pid" # Must set this in named.conf as well
named_uid="bind"                # User to run named as
named_chrootdir="/var/named"    # Chroot directory (or "" not to
auto-chroot it)
named_chroot_autoupdate="YES"   # Automatically install/update chrooted
                                # components of named. See /etc/rc.d/named.
named_symlink_enable="YES"      # Symlink the chrooted pid file

As you can see, your named_uid and named_chrootdir are not needed, that
is the default.

The thing causing your issue is named_chroot_autoupdate="YES" (the
default) and it is correct to do so, you should not be changing these
without very good reason.

Philip M. Gollucci ([EMAIL PROTECTED])
Senior System Admin - Riderway, Inc. /
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB  B89E 1324 9B4F EC88 A0BF

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to