On 2024-05-29 16:13:05 -0000, Curt wrote: > On 2024-05-29, Vincent Lefevre <vinc...@vinc17.net> wrote: > > During the latest shutdown: > > > > May 29 01:55:05 qaa systemd[1]: Stopping session-2.scope - Session 2 of > > User vinc17... > > [...] > > 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 user@1000.service - User Manager > > for UID 1000... > > [...] > > > > Note: I had set DefaultTimeoutStopSec=20s because then is normally > > sufficient. > > > > The mutt process was running in GNU Screen. The current mailbox > > was just a local one. Mutt does no network connections (I do not > > use IMAP). I general, I quit it before logging out, but this time, > > it seems that I forgot. > > > > But I don't understand why there was a timeout. Does this mean that > > mutt didn't react to SIGTERM? Any reason? > > > > sudo journalctl -b-1?
See above. There's nothing else about mutt in the journal. -- 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)
