Thank you!
This helped us solve a major headache we had with processes hanging
around after the tests have finished:
https://github.com/Bailador/Bailador/issues/194
regards
Gabor
On Sat, Jul 15, 2017 at 10:23 AM, Gabor Szabo wrote:
> If I understand correctly, then this means Ctrl-C sends a SIGINT to
> both the main process I ran and the child process I created using
> Proc::Async. When I run kill -2 PID it only sends the SIGINT to the
> process I mentioned with PID.
> (
Hi,
Brandon, thanks for the explanation.
If I understand correctly, then this means Ctrl-C sends a SIGINT to
both the main process I ran and the child process I created using
Proc::Async. When I run kill -2 PID it only sends the SIGINT to the
process I mentioned with PID.
(Which in my case was t
On Sat, Jul 15, 2017 at 8:34 AM, Brandon Allbery
wrote:
> Ctrl-C sends SIGINT to all processes in the terminal's foreground process
> group. There is no concept of "current process" on a terminal; Unixlike
> systems are multitasking, and all processes in the process group have
> access to the ter
On Sat, Jul 15, 2017 at 6:50 AM, Gabor Szabo wrote:
> If I run this in one terminal and run "ps axuw" in another terminal I
> see 2 processes running.
> If I press Ctrl-C in the terminal where I launched the program, both
> processes are closed.
>
> OTOH If I run "kill PID" with the process ID of
Hi,
I don't understand this, and I wonder could shed some light on the situation?
I have the following experimental program:
use v6;
my $proc = Proc::Async.new($*EXECUTABLE, "-e", "sleep 2; say 'done'");
$proc.stdout.tap: -> $s { print $s };
my $promise = $proc.start;
await $promise;
If I r
