qubes-core-admin-linux/dom0-updates/qubes-dom0-updates.cron

#!/bin/bash

if [ "$(qvm-features dom0 service.qubes-update-check || echo 1)" != 1 ]; then
    exit 0
fi

# If no updates available - exit here
qubes-dom0-update --check-only >/dev/null && exit
RETCODE=$?

if [ "$RETCODE" -ne 100 ]; then
    echo "ERROR: Error checking for updates" >&2
    exit $RETCODE
fi

qvm-features dom0 updates-available 1
dom0-updates code 2013-03-16 17:54:00 +00:00			`#!/bin/bash`

dom0-updates: use qvm-service for disabling dom0 updates check Use the same mechanism as VMs - first it's compatible with Admin API (in contrary to flag files); second it ease handling it. Migrate old setting on package upgrade. 2018-11-02 01:28:58 +00:00			`if [ "$(qvm-features dom0 service.qubes-update-check \|\| echo 1)" != 1 ]; then`
dom0-updates: add flag file for disabling update check (#800) 2014-04-11 05:04:57 +00:00			`exit 0`
			`fi`
dom0-updates code 2013-03-16 17:54:00 +00:00
			`# If no updates available - exit here`
			`qubes-dom0-update --check-only >/dev/null && exit`
			`RETCODE=$?`

			`if [ "$RETCODE" -ne 100 ]; then`
			`echo "ERROR: Error checking for updates" >&2`
			`exit $RETCODE`
			`fi`

dom0-updates: use qvm-features to report dom0 updates Use the same as thing as VMs. 2018-11-02 00:58:27 +00:00			`qvm-features dom0 updates-available 1`