In systemd based systems, such as debian 8 and ubuntu 16.04, I have this issue whereby the machine will refuse to shut down if I forgot to stop my openvpn connection before sending the command to shut down.
The command I use to start my openvpn connection is:
sudo openvpn --config client.conf --script-security 2Is there a way I can change the command so systemd knows that it's okay to terminate it more quickly when the system is shutting down? Perhaps the alternative is to change systemd's timeout period to be much shorter? I would rather avoid any type of aliasing of my poweroff, halt, reboot, and shutdown commands.
3 Answers
I have used systemd for 5 months. Sometimes I get this problem.
To reduce the delay from the default value 90s (1min30s), it is in the /etc/systemd/system.conf file:
#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90sUncomment these line and change to any value you want. This solution just reduce time you have to wait. You should check your virtualbox daemon.
Second solution is install watchdog and enable it. It works for many people but it not works for me.
P/s: If you want to force poweroff. Let have a look at systemctl manpage.
2I stopped having this problem after I configured openvpn to run as a systemd unit.
I followed this section on the arch linux wiki:
It was also necessary to make other programs that run as sudo - systemd units as well (like wpa_supplicant was for me).
It does require knowledge and practice to start/stop/read logs of systemd units, but it definitely paid off.
" A start job running" is caused by etc/fstab having the wrong
Swap UUID (at least on my Ubuntu 16.04 Cinnamon)
do "sudo blkid" in a terminal to get the correct UUID for swap ,and then paste it into etc/fstab.
1
