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
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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Bill Wether:
> 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
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
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
