On 05/01/2018 03:50 PM, trueriver wrote: > 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?
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~~ > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c08ca02c-6b21-7f66-d5ea-c251a9ab7294%40maa.bz. For more options, visit https://groups.google.com/d/optout.
