You are not logged in.
since moving to Xubuntu 18.04i have been having a 2 minute wait to complete a shutdown or reboot. if i switch to a text-mode console and kill all the user processes (a hard kill -9) then a shutdown is quick. when a user logs out, there are still some of these processes still running. should this be the case? when i start up, my admin user autologs in. if i don't login any other user, a shutdown is quick. but if i even login one user and log it out, a shutdown has that 2 minute wait. even if i leave it logged in, there is that 2 minute wait. any idea what i should do? this is driving me bonkers.
Offline
From your activity in the forum, I can say you know much more about software than me. But xfce does leave many user processes running after logout and I think that's some flaw in xfce4-session.
If you install something simple like icewm then you can test by logging into it after a fresh boot and then shutdown.
Offline
You can use systemd to force kill all user processes on logout. Uncomment and set to "yes", the "KillUserProcesses" line in /etc/systemd/logind.conf.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
You can use systemd to force kill all user processes on logout. Uncomment and set to "yes", the "KillUserProcesses" line in /etc/systemd/logind.conf.
Thank for the resource, ToZ. But this doesn't seem like a solution as it's set to 'no' for a reason. But the Xfce session, which is started when we log into it, should obviously be terminated when we log out of it.
As for the issue in this post, maybe Skaperen could just log out and examine the running processes in another tty?
Offline
This is probably an Xfce bug. However, setting "KillUserProcesses=yes" will kill those errant processes on log out in the meantime. However, it's important to also understand the side effects of that setting.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
As for the issue in this post, maybe Skaperen could just log out and examine the running processes in another tty?
BTDT
there are many
but my real issue is how many of them stay after getting the SIGTERM from doing shutdown? the hard kill, SIGKILL, is delayed 2 minutes for a reason. i don't want to shorten that in case something is causing final saves by servers to be slow. if something is ignoring SIGTERM then it needs to be fixed. but just what that something is, i don't yet know.
Offline
[ Generated in 0.009 seconds, 7 queries executed - Memory usage: 535.76 KiB (Peak: 536.6 KiB) ]