Displaying 2 results from an estimated 2 matches for "named_chroot_autoupd".
2009 Jan 26
2
FreeBSD-7.1STABLE w/BIND-9.4.3-P1 start problem followup
...;
named_program="/usr/local/sbin/named" # path to named, if you want a different one.
named_flags="-c named.conf"
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
3./etc/rc./named stop
--------------------------------
named not running? (check /var/r...
2009 Jan 26
2
FreeBSD-7.1STABLE w/BIND-9.4.3-P1 start problem
...ot;-ss -l /etc/namedb/sandbox/dev/log"
#named_pidfile="/var/named/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
6.If I change port number like to 5353 then BIND start normally. I tried several times...