[Pkg-utopia-maintainers] Bug#978935: Bug#978935: network-manager: disconnect on upgrade

[Vincent Lefevre]

On 2021-01-01 12:58:48 +0100, Michael Biebl wrote:
> Am 01.01.21 um 01:19 schrieb Vincent Lefevre:
> > The name of the active connection could be stored in a file, so that
> > a reexec'ed daemon could pick the information. By active connection,
> > I mean the last connection chosen by the user, under the condition
> > that the user has not explicitly disconnected.
> 
> It's not that simple, unfortunately. There is much more state,
> especially in external daemons like wpasupplicant.

The name of the active connection and the associate device is shown
by "nmcli connection". This is everything what one needs to know.
I just had to do "nmcli device wifi connect <SSID>" to reconnect.

> > > Ethernet connections should not be torn down on a daemon stop.
> 
> See also this NEWS entry from the 1.6 release:
> 
> > * NetworkManager would now keep most connections up on shutdown
> >     (except Wi-Fi connections, VPN connections and other kinds
> >     that can't be assumed on startup)

1.6, that's rather old! I suppose that various things have improved
since.

> The alternative of not restarting NM on upgrades isn't great either.

This could be another solution, asking the user to do that when safe.
This would not be the only case where a service is not restarted
automatically (there's udev).

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)