a bad configuration, mostly. people love to bash systemd but this is sensible, that it does not outright kill services that aren’t ready for that. if your computer shuts diwn slowly because of that, that is a configuration issue, that either a service or a mount does not stop cleanly.
Systemd waiting for <random thing> to terminate on shutdown is one of the reasons i’ve ditched it.
I don’t think I’ve ever had that issue. My PC shuts down within a few seconds. What kind of things would refuse to terminate?
Udev i think. Also, that’s a thing Systemd is (more or less) infamous for. Which is, why this joke weirded me out a bit.
a bad configuration, mostly. people love to bash systemd but this is sensible, that it does not outright kill services that aren’t ready for that. if your computer shuts diwn slowly because of that, that is a configuration issue, that either a service or a mount does not stop cleanly.
You could just configure the default timeout.
I solve that by holding my power button, not worth the hassle of ditching systemd for me
“A stop job is running for user manager for UID 1000” is such a pain :D
You can change the default wait from 90 seconds to something like 5 seconds.
/etc/systemd/system.conf.d/system.conf
[Manager] DefaultTimeoutStopSec=2s