...there are a few workarounds.... use killfam ( or the win32 version) to kill the pid and all it's children.....or you can spawn a command shell with ipc, and print the name of the executable you want to run to the shell's stdin.... probably something like the Win32::Job module is what you want....see Kill a process in Perl and killing on win32 and A killall for Windows

When you launch a child process, Perl has no way of knowing what that process does once it starts. Specifically, if you launch a shell, it has no way of knowing what processes (if any) it will later launch.

If you want an certain application to be the child, don't launch a shell instead. This can be achieved using the multiple argument form of open3.

my $pid = open3(
    local *TO_CHLD,
    local *FR_CHLD,
    local *FR_CHLD_ERR,
    'prog', $arg1, $arg2
);
[download]

It's also less work to use the multiple argument form since it saves from converting $arg1 and $arg2 from text into shell literals.

(I bet you didn't do that, so you probably have a bug and a security vulnerability in your code.)

thanks for your response i use: my $pid = open3(...) So, what i need to do to kill spawned application?

In unix, you'd do:

kill TERM => $pid;
[download]

I think that works in Windows too.

Thanks. Everything works properly. I have not paid attention to multiple argument form. Really, if open3 called like open3($wtr,$rdr,$err,'command.exe -1 -2'); It produces cmd.exe.

I have not paid attention to multiple argument form.

I'm baffled. I told you that this is the solution to your problem, and you kept telling me it doesn't work even though you didn't even look at it.

Really, if open3 called like open3($wtr,$rdr,$err,'command.exe -1 -2'); It produces cmd.exe.

Yes. As previously explained, executing shell commands requires the shell. I also mentioned that applies to all OSes.