severity 432322 serious thanks On Sun, Dec 30, 2007 at 12:01:15PM +0100, Philipp Kern wrote: > On Mon, Jul 09, 2007 at 01:40:31PM +0100, Jon Dowland wrote: > > The last two times that the network-manager package has > > been upgraded, the process of doing so has killed my active > > network connections, including the ssh session with the > > controlling tty for the aptitude upgrade process: > That's so freakingly annoying. Couldn't you simple restart the daemon > through invoke-rc.d in postinst instead of stopping it in preinst > and bringing it back up in postinst? What's the reason for this > madness?
The Release Managers consider this bug to be RC for Lenny. Would it be possible to reload NetworkManager in a way not causing the network connection to break, i.e. without the devices being deconfigured? If all the files are replaceable while NetworkManager is still running `dh_installinit --no-start --no-restart-on-upgrade' together with invoke-rc.d in postinst (as n-m has an init script now, not just an event script) would be a start as it would reduce the downtime, but it will still deconfigure the interfaces shortly and take some time to reaquire the IP (on LAN) and on WiFi more time to reassociate to the AP, possibly needing user intervention. And is #433087 (network-manager: Behaves poorly when dbus daemon is restarted) really the same issue? Dear maintainers, please provide some input on this issue. Kind regards, Philipp Kern -- .''`. Philipp Kern Debian Release Assistant : :' : http://philkern.de `. `' xmpp:[EMAIL PROTECTED] `- finger pkern/[EMAIL PROTECTED]
signature.asc
Description: Digital signature
