On 08.02.2017 00:57, Max Reitz wrote:
> Currently we only print progress information on retrieval of SIGUSR1.
> Some systems have a dedicated SIGINFO for this, however, so it should be
> handled appropriately if it is available.
>
> Buglink: https://bugs.launchpad.net/qemu/+bug/1662468
>
On 04/13/2017 04:38 PM, Max Reitz wrote:
> On 08.02.2017 00:57, Max Reitz wrote:
>> Currently we only print progress information on retrieval of SIGUSR1.
>> Some systems have a dedicated SIGINFO for this, however, so it should be
>> handled appropriately if it is available.
>>
>> Buglink:
On 08.02.2017 00:57, Max Reitz wrote:
> Currently we only print progress information on retrieval of SIGUSR1.
> Some systems have a dedicated SIGINFO for this, however, so it should be
> handled appropriately if it is available.
>
> Buglink: https://bugs.launchpad.net/qemu/+bug/1662468
>
On 08.02.2017 00:57, Max Reitz wrote:
> Currently we only print progress information on retrieval of SIGUSR1.
> Some systems have a dedicated SIGINFO for this, however, so it should be
> handled appropriately if it is available.
>
> Buglink: https://bugs.launchpad.net/qemu/+bug/1662468
>
On Wed, Feb 08, 2017 at 12:57:57AM +0100, Max Reitz wrote:
> Currently we only print progress information on retrieval of SIGUSR1.
> Some systems have a dedicated SIGINFO for this, however, so it should be
> handled appropriately if it is available.
>
> Buglink:
Currently we only print progress information on retrieval of SIGUSR1.
Some systems have a dedicated SIGINFO for this, however, so it should be
handled appropriately if it is available.
Buglink: https://bugs.launchpad.net/qemu/+bug/1662468
Signed-off-by: Max Reitz
---
Can