i got notification from an old client today that the search script suite i wrote ( a data file builder run via cron and a seach data file script ) stopped building the new datafile. i found an obvious error ( never let a non-perl user add an email address - the foo\@bar part ALWAYS gets forgotten! ) and thought i could call it fixed.

but no. it's not fixed. after about 2 hours of extra debugging, including wrapping everything in  eval loops to catch errors, the bloody thing still died. abruptly. with no error messages.

so i pulled the site to my local machine, and ran the databot, and everything worked like a charm.

which got me thinking -- the ISP's looking for 'runaway processes' and killing them.

so i'm wondering if it's feasible to try and catch  $SIG{KILL} in the script and try to ignore it.

i tried this, to no avail: 

local $SIG{KILL} = \&killed;

### some code 

sub killed {

        print "I got killed\n";

        }

[download]
an END block doesn't get executed when the script is killed. i tried: 
END {

    print "I got killed! \n ";
    
    }

[download]
but that didn't work either

i have other ideas for getting around this apparent rate cap . . . but i would like to know that the script is dying because of REAL errors, and not getting killed by some other process.

In reply to getting around an ISPs processing cap by geektron

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.