On Tue, Jan 30, 2024 at 11:43 AM Simon Lees <sflees@suse.de> wrote:
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
loginctl session-status 3 shows the same information without needing to know implementation details (scopes, slices, etc) or how exactly they are named. The practical problem is that you need to get this list when the system is shutting down.
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
Do you mean systemd-cgls? Because "systemctl status" most certainly does not show it.