On 2024-05-31 10:02:57 +0700, Max Nikulin wrote: > Do you mean that mutt properly exits unless it receives SIGTERM in the > course of shutdown process?
I think that this was not the first time I did a shutdown while Mutt was still running. But this was the first time it did not exit. > I would try to enable debug log in mutt. There is a chance that > networking is already disabled (or some other system unit important > for mutt is already stopped) when systemd tries to kill mutt first > time. No, according to the logs, the network was stopped after SIGKILL was sent to Mutt: May 29 01:55:26 qaa systemd[1]: session-2.scope: Stopping timed out. Killing. May 29 01:55:26 qaa systemd[1]: session-2.scope: Killing process 2990 (mutt) with signal SIGKILL. May 29 01:55:26 qaa systemd[1]: session-2.scope: Failed with result 'timeout'. May 29 01:55:26 qaa systemd[1]: Stopped session-2.scope - Session 2 of User vinc17. May 29 01:55:26 qaa systemd[1]: session-2.scope: Consumed 8h 17min 54.832s CPU time. May 29 01:55:26 qaa systemd[1]: Stopping systemd-logind.service - User Login Management... [...] May 29 01:55:26 qaa systemd[1]: Stopping NetworkManager.service - Network Manager... May 29 01:55:26 qaa NetworkManager[1238]: <info> [1716940526.2966] caught SIGTERM, shutting down normally. May 29 01:55:26 qaa NetworkManager[1238]: <info> [1716940526.2975] dhcp4 (eth0): canceled DHCP transaction Note that mutt is not the only case of timeout at shutdown. There's also May 25 22:53:32 qaa systemd[2230]: xdg-document-portal.service: State 'stop-sigterm' timed out. Killing. May 25 22:53:32 qaa systemd[2230]: xdg-document-portal.service: Killing process 116031 (xdg-document-po) with signal SIGKILL. May 25 22:53:32 qaa systemd[2230]: xdg-document-portal.service: Killing process 116037 (fusermount3) with signal SIGKILL. May 25 22:53:32 qaa systemd[2230]: xdg-document-portal.service: Main process exited, code=killed, status=9/KILL May 25 22:53:32 qaa systemd[2230]: xdg-document-portal.service: Failed with result 'timeout'. This one is a known issue: https://github.com/flatpak/xdg-desktop-portal/issues/999 I'm wondering whether there could be a same cause. -- 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)
