On Sat, Aug 22, 2009 at 10:47:16AM +1000, Craig Sanders wrote:
> when upgrading bind9, named is stopped until the upgrade is completed.
And there is no real way to make sure it stays working while the
libraries and such are changed out from under it, based on some of the
issues we ran into earlier in the bind9 train, which caused me to quit
trying to keep it running during a dist-upgrade.
> this could be a LONG time during an apt-get {dist-,dselect-,}upgrade,
> especially if there are many packaged being upgraded or if there are any
> debconf questions waiting to be answered.
And more reason to upgrade daemons in separation from the rest of the
machine.
> this has an obvious seriously detrimental and prolonged effect on the
> entire local network which depends on that nameserver.
> this is a repeat of an earlier bug (#453765), which was reported in Dec 2007
> and fixed in June 2008. It has come back.
And if I recall, it was intentionally reintroduced to fix an issue with
stopping the old daemon after the upgrade failed in a manner that made
it seem to be a bad thing to do.
> see also bug #471060 (debhelper, reported Mar 2008, fixed May 2008). a
> '--restart-after-upgrade' option was added to dh_installinit to provide
> a fix this behaviour. There was some suggestion that this might become
> the default behaviour but it looks like that hasn't happened.
I'll have to revisit the whole issue, but the switch to using
dh_installinit was done separate from the "don't bother trying to keep
it running through the upgrade" decision.
lamont
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
