Probably the best solution is to put in lots of code to catch various errors, then you know what died and how to fix it in 95 percent of the cases. For example, I am almost sure that Net::FTP does not actually do an exit when it has an error, so if you read the perldocs and figured out what it does do, you should be able to wrap it in if statements and the like and repair the error with letting the program die. for the case where an exit is called, there is always wrapping it in a eval and checking the value of $@ for the error that broke it. But there is always more than one way to do it
                - Ant

In reply to Re: Self resurrecting perl scripts by suaveant
in thread Self resurrecting perl scripts by RhetTbull

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &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.