You are not logged in.
I know there are other topics about systemd hanging on shutdown reboot, but my question is not about finding the cause of the hang, but in finding a way to tell systemd to wait less.
I've already the following set:
root@slimer# grep Sec= /etc/systemd/system.conf
#RuntimeWatchdogSec=0
#ShutdownWatchdogSec=10min
#TimerSlackNSec=
#DefaultTimerAccuracySec=1min
#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s
#DefaultRestartSec=100ms
#DefaultStartLimitIntervalSec=10s
RebootWatchdogSec=5s
ShutdownWatchdogSec=5s
DefaultTimeoutStopSec=5s
DefaultTimeoutStartSec=30s
DefaultTimeoutAbortSec=15sBut still sometimes, on shutdown. my system prints:
"A stop job is running for user manager for uid 1000"
2min5sec is set as the timeout.
Question is:
Is possible to cut it down?
Thanks.
Last edited by kokoko3k (2020-12-31 08:37:44)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
echo "DefaultTimeoutStopSec=10s" | sudo tee /etc/systemd/user.conf.d/timeoutstopsec.confOffline
Thank you, but as posted, I've already set it there to 5secs.
from man systemd:
When run as a system instance, systemd interprets the configuration file system.conf and the files in system.conf.d directoriesDo you think it is not supposed to work straight into system.conf anymore?
It seems it just *adds* that 5 seconds to a 2min timeout.
--edit--
I've just added the following to /etc/systemd/user.conf too:
DefaultTimeoutStopSec=5s
DefaultTimeoutAbortSec=5s
Let's hope it will do the trick...
Last edited by kokoko3k (2020-12-12 13:51:44)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
/etc/systemd/user.conf did the trick.
So far, so good, 5 seconds at most and it power off.
Marked as solved.
Last edited by kokoko3k (2020-12-31 08:38:39)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline