Skip to main content
Improve clarity that this is a workaround and that the default value is 90s. Remove startup time adjustment which is unrelated and can cause problems.
Source Link

It appears you canA workaround to this problem is to reduce thethis timeout in /etc/systemd/system.conf down from 90s to for example 10s:

DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s

and run the following command in terminal after making changes

$ systemctl daemon-reload

It appears you can reduce the timeout in /etc/systemd/system.conf:

DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s

and run the following command in terminal after making changes

$ systemctl daemon-reload

A workaround to this problem is to reduce this timeout in /etc/systemd/system.conf down from 90s to for example 10s:

DefaultTimeoutStopSec=10s

and run the following command in terminal after making changes

$ systemctl daemon-reload
the timeout settings will not be applied until and unless daemon is reloaded
Source Link

It appears you can reduce the timeout in /etc/systemd/system.conf:

DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s

and run the following command in terminal after making changes

$ systemctl daemon-reload

It appears you can reduce the timeout in /etc/systemd/system.conf:

DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s

It appears you can reduce the timeout in /etc/systemd/system.conf:

DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s

and run the following command in terminal after making changes

$ systemctl daemon-reload
Source Link
MightyPork
  • 1.2k
  • 12
  • 22

It appears you can reduce the timeout in /etc/systemd/system.conf:

DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s