The included code:

$SIG{'INT'} = sub { kill 'INT', $pid if $pid };

would be the Perl way to forward an interrupt. Except:

• the INT signal is normally sent to all processes in the group anyway, so you only forward it like this if you know the child went to some other process group already. And then, it probably went away to avoid this kind of interrupt.
• In a similar way, Windows also sends ^C (Ctrl+C) to all processes attached to that console
• signals do not really exist on Windows, and there this call to kill directly kills the process, no signal sent whatsoever

Or at least this is what the documentation says. Because when I try it out, nothing works as it should since I got on Windows...

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.