Your message dated Thu, 12 Feb 2009 23:56:06 +0400
with message-id <[email protected]>
and subject line Patch applied in 1:9.5.1.dfsg.P1-1
has caused the Debian Bug report #461464,
regarding bind9: stop should wait until bind is dead
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
461464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461464
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bind9
Version: 9.3.4-2etch1
Tags: patch
I've just had a problem where puppet (configuration management tool)
effectively ran: "bind9 stop; bind9 start". This failed as when start
was run, the stop hadn't finished.
This patch uses rndc to ask for the pid and waits for it to die.
The 2 second hack is then removed (replaced by 1 second in a loop hack).
Adrian
--
Email: [email protected] -*- GPG key available on public key servers
Debian GNU/Linux - the maintainable distribution -*- www.debian.org
--- bind9.orig 2008-01-18 15:50:21.000000000 +0000
+++ bind9 2008-01-18 15:58:27.000000000 +0000
@@ -46,7 +46,13 @@
if [ "X$RESOLVCONF" != "Xno" ] && [ -x /sbin/resolvconf ] ; then
/sbin/resolvconf -d lo.named
fi
- /usr/sbin/rndc stop
+ pid=`/usr/sbin/rndc stop -p | sed -n 's/^pid: //; T; p'`
+ if [ "$pid" ]; then
+ while kill -0 $pid 2>/dev/null; do
+ log_progress_msg "waiting for pid $pid to die"
+ sleep 1
+ done
+ fi
log_end_msg $?
;;
@@ -58,7 +64,6 @@
restart)
$0 stop
- sleep 2
$0 start
;;
--- End Message ---
--- Begin Message ---
Version: 1:9.5.1.dfsg.P1-1
The patch is applied in 1:9.5.1.dfsg.P1-1, but this isn't mentioned
in changelog.
--- End Message ---
