On 10/12/2015 06:25 AM, Michal Privoznik wrote:
> So we have this mechanism that on SIGUSR1 the virtlockd dumps its
> internal state into a JSON file, reexec itself and the reloads
> the internal state back. However, there's a bug in our
> implementation:
>
> (gdb) signal SIGUSR1
> Continuin
So we have this mechanism that on SIGUSR1 the virtlockd dumps its
internal state into a JSON file, reexec itself and the reloads
the internal state back. However, there's a bug in our
implementation:
(gdb) signal SIGUSR1
Continuing with signal SIGUSR1.
[Thread 0x7fd094f7b700 (LWP 10602) exit
