On 12/13/18 8:10 PM, mike wrote:
On Thursday, December 13, 2018 at 2:52:06 AM UTC+2, reby wrote:IIRC sys-net sometimes can be stubborn if one is not patient enough so use qvm-kill if in a hurry ..... personally I don't see a downside of it autostarting, though I guess one might have reasons to not want that, any wayMy sys-net starts when I log in to Qubes (not during boot as it would if it was configured to start on boot). It also starts immediately after being shut down. Same is for sys-firewall. Maybe I wouldn't even have noticed that, because normally I want it to always be on, but I currently have a particular reason I would like to shut it down and can't. :)
Any VM used by another for networking will be started as dependency whenever you start the other.
Moreover I guess the update checks might cause a network VM start.If you have a lot of qvm-run calls pending in the background (e.g. if you're doing dom0 scripting), it'll also cause the target VM to constantly restart unless you used the -n option (which is not the default).
qvm-pause could be an option without these issues. KR David -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6162a1f5-abf2-2cef-165a-1c0674113231%40hackingthe.net. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
