On Mon, Aug 24, 2009 at 11:05:00AM +1000, Craig Sanders wrote:
> i've already mentioned bug #453765.
And interestingly, all of the code added when that was closed is still
there. And the commit log really tells the story - upgrading BIND9 from
something older than 1:9.5.0.dfsg-2
Leave named running during update.
BIND can safely continue to run during the upgrade process, just restart it
in postinst if it is running.
Of course, we can't actually do anything about the prerm script currently
on the machine... :-(
Addresses-Debian-Bug: 453765
Signed-off-by: LaMont Jones <lam...@debian.org>
OTOH, that commit lacks changes to not stop it on upgrade.
> an even better option is for the bind9 package to actually make some
> effort to minimise downtime by restarting after upgrade rather than
> stopping early and starting late.
And it would appear that I was misremembering - it must have been a
different package.
> and i can not fathom why there's so much resistance to just adding
> '--restart-after-upgrade' to the call to dh_installinit. it's a very
> simple fix with no downside.
Pretty sure --restart-after-upgrade wasn't something I was aware of at
the time.
> it was fine for years before i reported the problem the first time in
> Dec 2007 (bug #453765), and has been fine since that bug was closed in
> June 2008 up until the recent change that re-introduced the bug.
Interestingly, I'm pretty sure it was "not fine" for the interim, given
the missing prerm code.
lamont
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
