Re: restart named; missing TCP socket

2012-12-13 Thread Kevin Oberman
On Wed, Dec 12, 2012 at 6:04 AM, Tony Finch wrote: > Mark Andrews wrote: >> >> You need to wait for named to stop >> >> p=`rndc stop -p | awk '{print $2}'` >> while kill -0 $p >> do >> sleep 1 >> done >> /etc/rc.d/rc.named start This looks like FreeBSD. If so, just use 'service named rest

Re: restart named; missing TCP socket

2012-12-12 Thread Tony Finch
Mark Andrews wrote: > > You need to wait for named to stop > > p=`rndc stop -p | awk '{print $2}'` > while kill -0 $p > do > sleep 1 > done > /etc/rc.d/rc.named start Thanks. Tony. -- f.anthony.n.finchhttp://dotat.at/ Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6

Re: restart named; missing TCP socket

2012-12-12 Thread Mark Andrews
In message , Tony F inch writes: > I have had a few instances recently when named has failed to re-open its > TCP listening socket after a restart. This is particularly likely if I > try to bounce it quickly with a command line like > > # rndc stop; /etc/rc.d/rc.named start You need to wait for

RE: restart named; missing TCP socket

2012-12-12 Thread Lightner, Jeff
water@lists.isc.org] On Behalf Of Tony Finch Sent: Wednesday, December 12, 2012 8:20 AM To: bind-users@lists.isc.org Subject: restart named; missing TCP socket I have had a few instances recently when named has failed to re-open its TCP listening socket after a restart. This is particularly likely

restart named; missing TCP socket

2012-12-12 Thread Tony Finch
I have had a few instances recently when named has failed to re-open its TCP listening socket after a restart. This is particularly likely if I try to bounce it quickly with a command line like # rndc stop; /etc/rc.d/rc.named start The servers in question are recursive (apart from a few local zon