On 1/30/24 01:50, Simon Becherer wrote:
Hi,
since a couple of weeks always when i try to shutdown my tumbleweed (not actual updated, so an update is not the case of the problem) a delay for the shutdown:
"a stop job is running for session 3 of user simon"
i am user "simon" and i have before closed kde regularly with the shut down option and nothing left open.
its a "normal" desktop kde system, with connections to and from it, inside the lan over nfs and sometimes over ssh. but the most times 3 tumbleweed computers who are running inside this lan who have theoretically access, i and my wife are the operators, so nobody should have "logged in" when i shut down. from outside the internet there should be nothing open to come in to the lan.
how could i investigate what is here "session3" and still running?
sudo systemctl status session-3.scope I just created a session-3 by sshing in from a second machine, it looks something like this ├─session-3.scope │ ├─2250 "sshd: simon [priv]" │ ├─2252 "sshd: simon@pts/15" │ └─2253 -fish sudo systemctl status will list all users so you can work out who the session belongs to by looking at something like this. └─user.slice └─user-1000.slice ├─session-1.scope │ ├─ 727 /opt/hexchat/bin/hexchat -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B