On 04/06/2024 07:29, Vincent Lefevre wrote:
On 2024-05-31 19:05:45 +0700, Max Nikulin wrote:
Do you see an attempt to send SIGTERM to mutt before timeout and SIGKILL?
Unfortunately, there was no information from systemd. Some daemons
log a received SIGTERM, but mutt isn't a daemon.
It is still a part of some systemd.service, try systemd-cgls. If mutt
does not receive SIGTERM then it has no chance to stop. Perhaps that log
entry just tells that a signal is sent to the whole cgroup.
What other processes survived first step? Are there something suspicious
before SIGKILL stage?
According to the journalctl output, only mutt survived (the only
process to receive a SIGKILL). And nothing suspicious.
In the previous message you wrote about xdg-document-portal.
Perhaps timeouts are inconsistent for system and user services, so
user@.service is killed before SIGTERM and SIGKILL stages completed
withing the systemd user session. However I still expect SIGTERM before
SIGKILL.
You may start a shell script that logs SIGTERM, but does not exit, to
test if behavior is similar to your mutt issue.
