On Apr 25, 2022, at 21:17, Tom Horsley <horsley1953@xxxxxxxxx> wrote: > >> On Mon, 25 Apr 2022 16:45:41 -0400 >> Jonathan Billings wrote: >> >> if you want it to, it will terminate all user processes *for that session* when it logs out > > This only recently started working moderately well. If I ever ssh'ed into > my desktop for a separate login session, systemd would create some sort > of systemd user daemon that would hang around forever even after I > logged out of the ssh session. Then when I tried to reboot the system, > it would take something like 5 minutes to timeout waiting for the > user daemon to terminate. I think it is finally better now, but it took > years. I started using my own special reboot script that would search > for and kill all systemd user daemons before trying to reboot :-). I believe KillUserProcesses is “no” by default, so it is unlikely to be related. I had to enable it on our systems. The systemd --user daemon does hang around though, and it is likely it is waiting on terminating some pesky user process that wasn’t terminating properly. It isn’t the blocking process, it is the daemon trying to terminate it. -- Jonathan Billings _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
