sys-net self starts about 40min after boot

[trueriver]

I do not want my laptop to boot up and immediately look for a network connection.

Therefore I set sys-net and sys-firewall NOT to start at boot.

The only domain that is currently set to start at boot time is one that has not network connection. And dom0 of course ;)

At boot time those indeed are the only machines that are started.

I have twice noticed at around dom0 uptime = 40min that sys-net starts and connects (or tries to). This is exactly what I am trying to avoid.

I am not yet entirely sure this is not just some clumsiness of my own, so am not ready to declare an issue.

Question: is there some auto-update feature (of dom0, or templates, or whatever) that may be automatically asking for a network connection?

Regards
River~~

[Ivan Mitev]

I think I've read somewhere that sys-net would start on-demand on 4.0 if
it's not running, but I may be wrong.

See if this helps:

in dom0:

- `qubes-prefs check_updates_vm false`

- `touch /var/lib/qubes/updates/disable-updates`

(the latter is so that /etc/cron.daily/qubes-dom0-updates.cron exits early).



>
> Regards
> River~~
>

[Chris Laprise]

See this issue:
https://github.com/QubesOS/qubes-issues/issues/3588

--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

[trueriver]

THanks for the responses
Chris Laprise said

> See this issue:
> https://github.com/QubesOS/qubes-issues/issues/3588

Yes my observations are consistent with sys-net being triggered by an on-the-hour cron. I have commented on that issue and mark this thread as complete