Right; ActivePerl doesn't _really_ fork when you use fork, so that example's not going to work for you. I'm pretty sure the pseudo-forked processes they use wouldn't handle signals, even if they were supported under NT, which they aren't :)
This is from the ActivePerl docs, under "Windows Quirks".
Why doesn't signal handling work on Windows?
Signals are unsupported by the Win32 API. The C
Runtime provides crude support for signals, but there
are serious caveats, such as inability to die() or exit()
from a signal handler. Perl itself does not guarantee that
signal handlers will not interrupt critical operations such
as memory allocation, which means signal invocation may
throw perl internals into disarray. For these reasons,
signals are unsupported at this time.
Try this script on a Linux box, or, if you're VERY brave, with a native cygwin perl. But be warned, with 5.6.1 under Cygwin, playing with that kind of script causes bad things to happen for me.
--
Mike
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.