Kevin Oberman wrote:
Date: Mon, 24 Aug 2009 15:01:53 -0500
From: Guy Helmer <ghel...@palisadesys.com>
Sender: owner-freebsd-sta...@freebsd.org
Lisa Besko wrote:
We had an issue with the /etc/rc.d/named script this morning where it
looped/hung in the wait_for_pids subroutine. We run a job to restart
named which calls the /etc/rc.d/named script with a stop command. For
some reason named did not stop properly and the process continued to
list PIDs from the wait_for_pids subroutine forever. Has anyone ever
encountered this before?
We are running 7.2 stable and bind 9.4.3-P3 on an AMD system.
Thanks,
LB
Has named's rc script worked OK before? If not, it might be a config
problem like mine. I found that after I added
pid-file "/var/run/named/pid";
to the options section of my named.conf file, the rc script was able to
stop/restart a running named process.
Hope this helps,
Guy Helmer
Odd. Unless something (like /etc/defaults/rc.conf) else was touched,
this should not be required. It is already in /etc/defaults/rc.conf, a
file that should be modified only with a really good understanding of
the way it is used.
Here is the current defaults for named:
named_pidfile="/var/run/named/pid" # Must set this in named.conf as well
You probably should only put the line 'named_enable="yes"' into
/etc/rc.conf. Do not put it into /etc/defaults/rc.conf or change the
entry in that file! Changes should only be made to /etc/rc.conf.
Right, and it looks like the default pid file in named is
/var/run/named.pid, so until I added a pid-file line to named.conf to
match named_pidfile's setting in /etc/default/rc.conf, the named rc
script wasn't successfully stopping/restarting named.
Guy
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
