dice@maelcum:~ % ll /etc/rc.d/named
ls: /etc/rc.d/named: No such file or directory
dice@maelcum:~ % pkg info -x bind
bind-tools-9.18.5
bind916-9.16.31
dice@maelcum:~ % ll /usr/local/etc/rc.d/named
-rwxr-xr-x 1 root wheel 12409 Jul 24 02:14 /usr/local/etc/rc.d/named*
dice@maelcum:~ % freebsd-version -uk
13.1-RELEASE
13.1-RELEASE
ls -l /etc/rc.d/named /usr/local/etc/rc.d/named
ls: /etc/rc.d/named: No such file or directory
-rwxr-xr-x 1 root wheel 12409 Jul 23 22:32 /usr/local/etc/rc.d/named
service named restart
Stopping named.
Waiting for PIDS: 68802.
/usr/local/etc/rc.d/named: WARNING: named_pidfile: now determined from the conf file
Starting named.
service named stop
check there are no named(8) processes running, kill them if you have to. After making sure there's really nothing running any more you can start the service; service named start
.No, that's not it. It seems to me that in archlinux I manually prescribe the path so that named uses pid and not confStop the service, things probably got wacked because you had two different rc.d(8) scripts for the service. Afterservice named stop
check there are no named(8) processes running, kill them if you have to. After making sure there's really nothing running any more you can start the service;service named start
.
Remove this from rc.conf. And check ifCode:named_pidfile="/var/run/named/pid"
pid-file "/var/run/named/pid";
is in your named.conf.options {
// All file and path names are relative to the chroot directory,
// if any, and should be fully qualified.
directory "/usr/local/etc/namedb/working";
pid-file "/var/run/named/pid";
dump-file "/var/dump/named_dump.db";
statistics-file "/var/stats/named.stats