On 2024-12-27 14:03:19 +0100, Michael Biebl wrote: > Am 27.12.24 um 13:50 schrieb Vincent Lefevre: > > The restart should be smoother, so that the address resolution > > does not fail immediately, but waits for the ongoing restart to > > complete (with a success or failure). > > Not quite sure what mean by that or how NetworkManager could influence the > behaviour of an application that requires name resolution.
I mean that while the network is being restarted, as a user, I would expect the ongoing connections to wait for the network rather than fail immediately. In the present case, this was: Failed to open TCP connection to udd.debian.org:443 (getaddrinfo: Temporary failure in name resolution) so the restart of the wifi network should be done in such a way that getaddrinfo does not fail immediately. > Just throwing out some ideas: > If the apt hook fails to update its local database (for whatever reason), it > could touch a flag file (somewhere in /var/lib) and the next time > how-can-i-help is executed (by the user), how-can-i-help runs a refresh of > its database on-demand. > Or if the apt hook fails, it uses something like "systemd-run" to try the > update again in say 5min. But this is too late as I expect something in the terminal before I quit aptitude. But how-can-i-help could wait for the network to come back, though something at the system level (what I requested above) would be better, as all applications could benefit from it. -- Vincent Lefèvre <vinc...@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) _______________________________________________ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
