On Tuesday, March 20, 2018 at 3:08:13 PM UTC-4, awokd wrote: > On Tue, March 20, 2018 7:01 pm, Bill Wether wrote: > > Hi, all, > > > > > > In 3.2's dom0, typing > > > > > > qvm-run -a work konsole > > > > returns as soon as the VM has started up and the command has been issued. > > > > > > In R4, though, the Dom0 terminal just gets stuck--I can get it back with > > ctl-C, but that's pretty inelegant. I can use setsid, but that just > > disguises the problem since all those bash sessions are still there. > > > > Was this a design choice, is it a bug, or (as so often) pilot error? > > 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. 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? Cheers BillW -- 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/4d3f5447-f29b-485c-b114-e83336fb9923%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
