5e2bd5ea64
Prior to this commit, the qubes-core.service inherited systemd's default timeout value of 90 seconds. With slow hard disk drives, this caused the dom0 shut-down sequence to proceed even if some VMs were still not fully shut down at the time of dom0 shut down. This commit aims to avoid this issue by setting the service stop timeout to 180 seconds. Signed-off-by: M. Vefa Bicakci <m.v.b@runbox.com>
22 lines
659 B
Desktop File
22 lines
659 B
Desktop File
[Unit]
|
|
Description=Qubes Dom0 startup setup
|
|
After=qubes-db-dom0.service libvirtd.service xenconsoled.service
|
|
# Cover legacy init.d script
|
|
|
|
[Service]
|
|
Type=oneshot
|
|
StandardOutput=syslog
|
|
RemainAfterExit=yes
|
|
# Needed to avoid rebooting before all VMs have shut down.
|
|
TimeoutStopSec=180
|
|
ExecStart=/usr/lib/qubes/startup-misc.sh
|
|
ExecStop=/usr/bin/qvm-shutdown -q --all --wait
|
|
# QubesDB daemons stop after 60s timeout in worst case; speed it up, since no
|
|
# VMs are running now
|
|
ExecStop=-/usr/bin/killall qubesdb-daemon
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|
|
Also=qubes-block-cleaner.service qubes-meminfo-writer.service qubes-qmemman.service
|
|
Alias=qubes_core.service
|