core-agent-linux/vm-systemd/qubes-update-check.service

[Unit]
Description=Qubes check for VM updates and notify dom0
ConditionPathExists=/var/run/qubes-service/qubes-update-check
After=qubes-qrexec-agent.service

[Service]
Type=oneshot
ExecStart=-/usr/lib/qubes/upgrades-status-notify
vm: notify dom0 when updates available in VM (#475) 2012-05-01 01:14:04 +02:00			`[Unit]`
			`Description=Qubes check for VM updates and notify dom0`
			`ConditionPathExists=/var/run/qubes-service/qubes-update-check`
systemd: make sure that update check is started only after qrexec-agent 2015-11-11 01:19:33 +01:00			`After=qubes-qrexec-agent.service`
vm: notify dom0 when updates available in VM (#475) 2012-05-01 01:14:04 +02:00
			`[Service]`
			`Type=oneshot`
systemd: don't mark updates check service failed Even if update check fails for some reason (network problem, apt-get lock being held etc), don't mark the service as failed. The update check mechanism is designed this way to not worry about such single failures - other VM(s) may still check and report updates availability. Fixes QubesOS/qubes-issues#1889 2016-07-16 15:30:40 +02:00			`ExecStart=-/usr/lib/qubes/upgrades-status-notify`