Actually I do understand your point of view... and agree with you for the most part.
even if the process goes into lala land, a separate process will kill it, start a new process which will examine what was done, undo whatever was 'messed up', and continue with the task. The overall effect would be no worse than performing kill -SIGKILL (-9).
However, if I just wrote a routine to restart the system call without any other failsafe in place, then that would be bad and irresponsible.
For most tasks, the unsafe signals are undesirable.. on certain tasks, they are unavoidable and necessary. The fact that they are unsafe is a failure of the Perl engine... so we have to make do, for now, with what we have and build contingency plans for using the unsafe signals.
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.