Re: [PATCH] remote_daemon: Don't run virStateCleanup() if virStateReload() is still running

On 5/19/22 15:27, Martin Kletzander wrote: > On Mon, Apr 25, 2022 at 11:06:06AM +0200, Michal Privoznik wrote: >> When a SIGHUP is received a thread is spawned that runs >> virStateReload(). However, if SIGINT is received while the former >> thread is still running then we may get into problematic

Re: [PATCH] remote_daemon: Don't run virStateCleanup() if virStateReload() is still running

On Mon, Apr 25, 2022 at 11:06:06AM +0200, Michal Privoznik wrote: When a SIGHUP is received a thread is spawned that runs virStateReload(). However, if SIGINT is received while the former thread is still running then we may get into problematic situation: the cleanup code in main() sees drivers

Re: [PATCH] remote_daemon: Don't run virStateCleanup() if virStateReload() is still running

On 5/5/22 13:10, Michal Prívozník wrote: > On 4/25/22 11:06, Michal Privoznik wrote: >> When a SIGHUP is received a thread is spawned that runs >> virStateReload(). However, if SIGINT is received while the former >> thread is still running then we may get into problematic >> situation: the cleanup

Re: [PATCH] remote_daemon: Don't run virStateCleanup() if virStateReload() is still running

On 4/25/22 11:06, Michal Privoznik wrote: > When a SIGHUP is received a thread is spawned that runs > virStateReload(). However, if SIGINT is received while the former > thread is still running then we may get into problematic > situation: the cleanup code in main() sees drivers initialized > and

[PATCH] remote_daemon: Don't run virStateCleanup() if virStateReload() is still running

When a SIGHUP is received a thread is spawned that runs virStateReload(). However, if SIGINT is received while the former thread is still running then we may get into problematic situation: the cleanup code in main() sees drivers initialized and thus calls virStateCleanup(). So now we have two