Idealistically - you supposed to figure out what wrong with particular service that causing long shutdowns, by using: journalctl -b -1 -e or something like that. You can also use systemd-analyze blame to do the opposite and figure out what causing long startup.
But if you a normal human being that doesn’t have weeks to figure out bugs on kernel level with AMDGPU power management, then there a simpler solution - you just need to lower timer. In file:
/etc/systemd/system.conf
Uncomment (remove #) this line and set it either in minutes or seconds:
DefaultTimeoutStopSec=10s
I really don’t understand why default is so high. Even on old and weak hardware shut down shouldn’t take too much time.
Idealistically - you supposed to figure out what wrong with particular service that causing long shutdowns, by using:
journalctl -b -1 -eor something like that. You can also usesystemd-analyze blameto do the opposite and figure out what causing long startup.But if you a normal human being that doesn’t have weeks to figure out bugs on kernel level with AMDGPU power management, then there a simpler solution - you just need to lower timer. In file:
/etc/systemd/system.confUncomment (remove #) this line and set it either in minutes or seconds:
DefaultTimeoutStopSec=10sI really don’t understand why default is so high. Even on old and weak hardware shut down shouldn’t take too much time.
Thank you so much! Hopefully this works.