On Wed, March 21, 2018 2:33 am, Bill Wether wrote: > On Tuesday, March 20, 2018 at 3:08:13 PM UTC-4, awokd wrote:
>> Design choice. Try appending a " &" after the command string. >> > > > Could you give me a few more words about that? Running it in the > background is like setsid, except that the cruft stays in the same > process. Marek said somewhere (mailing list? issue?) that this was a design choice for 4. Can't recall exactly where though! > ISTM that 'qvm-run' should just run the program in the VM, if necessary > starting the VM first. What's it doing, waiting for a return code? I believe it's waiting on a return code, yes. It makes sense for running one-shot programs in a VM. Of course, longer running programs involving user input will take longer to return on exit. Sorry, don't have much more details than that. -- 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/2deba4b475223875ef432b0c8f6d74a1.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
