core-admin/linux/systemd/qubes-core.service
Marek Marczykowski-Górecki bae493d015
Kill remaining qubesdb-daemon instances after shutting down all the VMs
It may happen (especially when VM doesn't close cleanly and needs to be
killed) that qubesdb-daemon will not notice VM shutdown immediately.
Normally it would stop after 60s timeout, but speed it up in case of
system shutdown

QubesOS/qubes-issues#1425
2015-11-15 02:06:19 +01:00

20 lines
581 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
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