--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAL%3DE%3DjTei5TqEq%2BiEcOHRC18c74KjL5rMLMY1q1W-%2B4yWU65Uw%40mail.gmail.com.
I'm starting a process using ProcessBuilder in an integration test. The problem is that the process is a script that spawns child processes and Process.destroy(Forcibly) does not kill child processes.
interesting - did not know that would work reliably on Windows?
/max
--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAL%3DE%3DjQtkEs78vMJCUbyUhpgzxerNt4%3D2Dv5HrmDKRzeJPAcNw%40mail.gmail.com.
My biggest battle been when processes launched via a cmd/bat etc. then it at least
seem like that script can be waiting on output from a process it launched but
its not a true child and thus gets to be a live zombie if you force-stop the script.
Guess no better way than to test it :)
/max
https://xam.dk/about
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/BFB0AE00-F389-47E8-8D7B-5D03E05C7D1F%40redhat.com.