Control: severity -1 normal Am 01.01.21 um 01:19 schrieb Vincent Lefevre:
On 2020-12-31 20:22:56 +0100, Michael Biebl wrote:Am 31.12.20 um 18:37 schrieb Vincent Lefevre:During the upgrade, network-manager disconnected, so that I completely lost the network connection. Fortunately, I was in front of my machine, but this means that a remote upgrade can make the machine unavailable!I might be mistaken, but afaics, this has always been the case for WiFi connections (as it is not really possible to carry the state across daemon reexecs). Are you saying this is not the case?I've been using NetworkManager only since July on my laptop. I've checked my logs, and this was the first time I upgraded NetworkManager over WiFi. Before using NetworkManager, I've never had such an problem, IIRC. When my machine was connected via WiFi, I was using wicd. I suppose that it could handle the reconnection, or this would mean that I upgraded it only over Ethernet (I don't remember). 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.
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)
The alternative of not restarting NM on upgrades isn't great either. Not sure if there is anything that can be done about this.
OpenPGP_signature
Description: OpenPGP digital signature
