> On 24 Apr 2021, at 20:56, Dave Voutila wrote:
>
>
> Dave Voutila writes:
>
>> Dave Voutila writes:
>>
>>> vmd(8) users of tech@,
>>>
>>> NOTE: I have no intention to try to commit this prior to 6.9's release
>>> due to its complexity, but I didn't want to "wait" to solicit testers or
>>>
Dave Voutila writes:
> Dave Voutila writes:
>
>> vmd(8) users of tech@,
>>
>> NOTE: I have no intention to try to commit this prior to 6.9's release
>> due to its complexity, but I didn't want to "wait" to solicit testers or
>> potential feedback.
>
> Freeze is over, so bumping this thread with
Dave Voutila writes:
> vmd(8) users of tech@,
>
> NOTE: I have no intention to try to commit this prior to 6.9's release
> due to its complexity, but I didn't want to "wait" to solicit testers or
> potential feedback.
Freeze is over, so bumping this thread with an updated diff below.
>
> I
vmd(8) users of tech@,
NOTE: I have no intention to try to commit this prior to 6.9's release
due to its complexity, but I didn't want to "wait" to solicit testers or
potential feedback.
I noticed recently that I could not have two vmctl(8) clients "wait" for
the same vm to shutdown as one would
On Mon, Dec 03, 2018 at 06:22:14PM +0100, Claudio Jeker wrote:
> This adds a feature to vmctl/vmd to wait for a VM to stop.
> It is a feature usable in many situation where you wait for a VM to halt
> after work is done. This is more or less vmctl stop -w without
> sending the termination to the
This adds a feature to vmctl/vmd to wait for a VM to stop.
It is a feature usable in many situation where you wait for a VM to halt
after work is done. This is more or less vmctl stop -w without
sending the termination to the VM.
There is only one vmctl that can wait so if a second one comes in
