Hi, On Mon, Mar 23, 2026 at 11:04:08PM +0000, alain williams wrote: > I removed generation of all of these messages and the recovery file is > generated. So it seems that when the system is shutting down any terminal > output causes the program to be immediately terminated or possibly just > suspended and then later terminated.
[…] > So: problem with systemd ? What do you think ? I don't fully understand the situation, but if it is that: 1. All your processes receive a SIGTERM 2. Your editor writes a message about that to your terminal 3. Your terminal already exited because it got a SIGTERM 3. So your editor never manages to write its message and then doesn't follow through with writing open buffers to recovery file …then I would say that the bug is in the editor because writes to file descriptors aren't guaranteed to succeed or even to not block forever, so should it really be blocking an emergency action on the success of that? If we were to argue that the bug is in systemd, what would be the systemd fix to that situation? But perhaps I have misunderstood. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
