I agree that services/-ers should be restarted on install/upgrade, but NOT services/-ers that will cut the controlling console. That's why ssh isn't restarted 'the old fasioned way'. I can't remember exactly when, but it was discussed in Debian a _very_ long time ago.
Same arguments goes for NetworkManager to. It is/can be possible to end up with a inconsistent system if this happens. NetworkManager _will_ (eventually - your way or the current way) restore the connection, but then it's (can be) to late - the controlling console/tty is already cut! Hence, I do NOT agree with 'wishlist'! NetworkManager should only restart if controlling console is not on a network console/tty. If possible, the service could be restarted after apt/dpkg have finished it's run, but I don't think that's possible at the moment. -- network-manager is restarting the network on upgrade https://bugs.launchpad.net/bugs/107013 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
