On Fri, Mar 20, 2026 at 11:02:12AM -0400, Daniel Sterling wrote: > On Fri, Mar 20, 2026 at 10:53 AM didier gaumet <[email protected]> > wrote: > > I was thinking these requests are treated by > > systemd-halt.service(8)? > > unfortunately it's likely that systemd is killing these (non-service) > processes well before the systemd-shutdown binary runs. > > if anyone knows / can point to docs on how systemd handles non-service > processes resulting from user logins, that would be a starting point. > > after understanding that, the next thing to understand would be how > systemd on debian is configured to terminate these processes, > potentially on both logout and on reboot (and if there is a > difference)
I followed: https://wiki.debian.org/systemd Solution #2: Increase verbosity via /etc/systemd/system.conf Yes: much more in the journal. It tells me that it is 'sending SIGTERM to remaining processes' but nothing about processes before that. I am testing this in a virtual machine under QEMU. The machine shuts down quite quickly, I wonder if SIGKILL is sent too quickly after SIGTERM. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>
