core-admin/linux/systemd/qubes-core.service

[Unit]
Description=Qubes Dom0 startup setup
After=qubes-db-dom0.service libvirtd.service xenconsoled.service qubesd.service qubes-qmemman.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-meminfo-writer-dom0.service qubes-qmemman.service
Alias=qubes_core.service
dom0/init: implement systemd unit files They cover standard init.d scripts when system have systemd, so can be placed both in one package. 2013-01-27 00:04:40 +01:00			`[Unit]`
			`Description=Qubes Dom0 startup setup`
Fix qubes-core.service ordering The service needs to be started after qubesd and qubes-qmemman to be able to start domains. The same applies on shutdown - should be ordered before shutting down qubesd. 2017-10-28 22:42:59 +02:00			`After=qubes-db-dom0.service libvirtd.service xenconsoled.service qubesd.service qubes-qmemman.service`
dom0/init: implement systemd unit files They cover standard init.d scripts when system have systemd, so can be placed both in one package. 2013-01-27 00:04:40 +01:00			`# Cover legacy init.d script`

			`[Service]`
			`Type=oneshot`
dom0/systemd: typo fix 2013-02-12 01:37:04 +01:00			`StandardOutput=syslog`
dom0/init: implement systemd unit files They cover standard init.d scripts when system have systemd, so can be placed both in one package. 2013-01-27 00:04:40 +01:00			`RemainAfterExit=yes`
qubes-core.service: Do not shut down/reboot before all VMs have shut down 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> 2017-03-14 15:34:57 +01:00			`# Needed to avoid rebooting before all VMs have shut down.`
			`TimeoutStopSec=180`
dom0/init: implement systemd unit files They cover standard init.d scripts when system have systemd, so can be placed both in one package. 2013-01-27 00:04:40 +01:00			`ExecStart=/usr/lib/qubes/startup-misc.sh`
			`ExecStop=/usr/bin/qvm-shutdown -q --all --wait`
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-14 23:43:38 +01:00			`# QubesDB daemons stop after 60s timeout in worst case; speed it up, since no`
			`# VMs are running now`
			`ExecStop=-/usr/bin/killall qubesdb-daemon`
dom0/init: implement systemd unit files They cover standard init.d scripts when system have systemd, so can be placed both in one package. 2013-01-27 00:04:40 +01:00
			`[Install]`
			`WantedBy=multi-user.target`
systemd: use appropriate meminfo-writer service for dom0 2017-05-31 04:28:45 +02:00			`Also=qubes-meminfo-writer-dom0.service qubes-qmemman.service`
dom0/init: implement systemd unit files They cover standard init.d scripts when system have systemd, so can be placed both in one package. 2013-01-27 00:04:40 +01:00			`Alias=qubes_core.service`