| Subject: | Lingering process from IPC::Cmd::run after alarm and interrupt (Win) |
Hello,
For Windows if the alarm or interrupt triggers, while in a call to IPC::Cmd::run(), the child process keeps running in the background. In contrast, a call to system() with descriptors redirected (null device - input, and some disk files - output), will pass the ^C to the child also.
Note the user is not aware of the issue since the child process runs with descriptors redirected.
Is it possible please to add some default signal handling during IPC::Cmd::run ?
Users of IPC::Cmd do not have the PID of the child process from run(), so I see no easy way to handle signals in user code.
Regards,
Timothy Madden