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.
Also, that’s a thing Systemd is (more or less) infamous for.
I’ve never heard of it before. I don’t know where it is infamous, I’ve never had that issue and of all the criticism I’ve seen levelled at Linux in general or systemd in particular, that has never been one. Maybe there was some configuration stuff, as the other reply mentioned?
Systemd waiting for <random thing> to terminate on shutdown is one of the reasons i’ve ditched it.
“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
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?
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.
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.
I’ve never heard of it before. I don’t know where it is infamous, I’ve never had that issue and of all the criticism I’ve seen levelled at Linux in general or systemd in particular, that has never been one. Maybe there was some configuration stuff, as the other reply mentioned?
You could just configure the default timeout.
2 min is still a bit much for a default. Make it 10 seconds.
I solve that by holding my power button, not worth the hassle of ditching systemd for me