I don’t know what comment section or post are talking about. Default timer for systemd on arch is 3 minutes (and I think it’s default for most distros). Whenever some service fails to quit on reboot, system will stuck for 3 minutes until systemd decide to kill it. I need to manually configure it lower to like, 10 seconds, cause there shit ton of services that always fails to quit.
And not like I’m using old pentium - my system build on AM5 with amd 7700x, 128gb of 5600MT\s ram and 7900xtx, with kingston nvme pcie4 ssd’s on top of that. It’s literally “best case scenario”.
How do you configure this? I have often encountered minute-long restarts most of which was fixed by adding a service to kill the wine server on shutdown, but still it sometimes happens.
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.
I don’t know what comment section or post are talking about. Default timer for systemd on arch is 3 minutes (and I think it’s default for most distros). Whenever some service fails to quit on reboot, system will stuck for 3 minutes until systemd decide to kill it. I need to manually configure it lower to like, 10 seconds, cause there shit ton of services that always fails to quit.
And not like I’m using old pentium - my system build on AM5 with amd 7700x, 128gb of 5600MT\s ram and 7900xtx, with kingston nvme pcie4 ssd’s on top of that. It’s literally “best case scenario”.
I guess the difference is that sigterm usually closes all the programs pretty quickly; but ITT I am learning that is not always the case!
How do you configure this? I have often encountered minute-long restarts most of which was fixed by adding a service to kill the wine server on shutdown, but still it sometimes happens.
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.