You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when send_interrupt is configured to true (for linux and unix only), the killCmd function sleeps for kill_delay before following up with a kill command as well.
If the target process honours the initial interrupt, cleans up and exits by itself, there is no need to sleep for a delay to try to kill a process that is no longer there. Air should instead wake up and continue as soon as the process has closed down, and only go on to send a kill to processes that ignore the interrupt or take too long to shut down.
The text was updated successfully, but these errors were encountered:
istyf
linked a pull request
Nov 1, 2024
that will
close
this issue
Currently when send_interrupt is configured to true (for linux and unix only), the killCmd function sleeps for kill_delay before following up with a kill command as well.
If the target process honours the initial interrupt, cleans up and exits by itself, there is no need to sleep for a delay to try to kill a process that is no longer there. Air should instead wake up and continue as soon as the process has closed down, and only go on to send a kill to processes that ignore the interrupt or take too long to shut down.
The text was updated successfully, but these errors were encountered: