FreeBSD test.ru 8.4-RELEASE-p4 FreeBSD 8.4-RELEASE-p4 #0 r255624: Tue Sep 17 10:58:52 YEKT 2013 # /etc/rc.d/named restart named not running? (check /var/run/named/pid). /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/sbin/named
Fix Summary and assign.
and now: m# /etc/rc.d/named start Starting named. /etc/rc.d/named: WARNING: failed to start named log: ---------------------------------------------------- Jan 7 00:26:15 us1 named[94800]: found 4 CPUs, using 4 worker threads Jan 7 00:26:15 us1 named[94800]: using 2 UDP listeners per interface Jan 7 00:26:15 us1 named[94800]: using up to 4096 sockets Jan 7 00:26:16 us1 named[94800]: loading configuration from '/usr/local/etc/named.conf' Jan 7 00:26:16 us1 named[94800]: open: /usr/local/etc/named.conf: file not found Jan 7 00:26:16 us1 named[94800]: loading configuration: file not found Jan 7 00:26:16 us1 named[94800]: exiting (due to fatal error) /usr/local/etc/named.conf - copied from /var/named/etc/namedb
The PR assignment never actually happened, so do it now.
So, at first, it seems you did not have: named_program="/usr/local/sbin/named" in your rc.conf, but that was fixed, right ? Now, it seems you've removed the /usr/local/etc/named.conf symlink to /etc/namedb/named.conf that is created when you install the port. You should reinstall the port, or create the symlink manually. If you use the chroot feature, you also need the same symlink in /var/named/usr/local/etc/named.conf.