Hello Christoph On 2006-11-03 Christoph Biedl wrote: > Christian Hammers wrote... > > > Regarding to the "fails to upgrade": as a restart of Quagga potentially > > means a loss of Internet connection for the router (and connected > > subnets) which is especially ugly if you administrate the server via ssh > > many people explicitly requested that Quagga will *not* be upgraded by > > default which was the reason I implemented this defaults-to-false > > debconf question. > > I understand your point: The admin should not upgrade without prior > thought. However, even if he has done the proper preparations like > logging in via a serial console, he still cannot upgrade unless he > changes the debconf setting - and back to the prior setting to avoid > shooting his foot the next time. This is a bit of a nuissance.
What do you mean by "chaning the debconf setting .. and back"? It's a normal Debconf question, it shows you a little text and asks for yes/no *every* time an upgrade attempt is made. It's none of the questions that Debconf tries to "remember" i.e. running "dpkg-reconfigure quagga" is unnecessary. > > So would you suggest to just clarify the wording of the question or > > what else to do? > > My suggestion: Check whether quagga is still running and abort the > upgrade only if it does. Print a warning then about probable loss of > connectivity during the upgrade and say that quagga has to be stopped > manually before upgrade to avoid a fatal situation. Checking if there are any daemons running can't hurt, though, I implement it. Such warning is already displayed via Debconf. bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
