fix: add windows signals SIGUSR2 & SIGUSR1 to terminate the process (#…

…1938) Authored-by: mohamed <[email protected]> Fixes: #1903, #1915, #1936, #1937, #1882, #1893
remy · Oct 19, 2021 · 61e7abd · 61e7abd
1 parent b449171
commit 61e7abd
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/lib/monitor/run.js b/lib/monitor/run.js
@@ -333,10 +333,10 @@ function kill(child, signal, callback) {
       }
     };
 
-    // We are handling a 'SIGKILL' POSIX signal under Windows the
+    // We are handling a 'SIGKILL' , 'SIGUSR2' and 'SIGUSR1' POSIX signal under Windows the
     // same way it is handled on a UNIX system: We are performing
     // a hard shutdown without waiting for the process to clean-up.
-    if (signal === 'SIGKILL' || osRelease < 10) {
+    if (signal === 'SIGKILL' || osRelease < 10 || signal === 'SIGUSR2' || signal==="SIGUSR1" ) {
       debug('terminating process group by force: %s', child.pid);
 
       // We are using the taskkill utility to terminate the whole