Err... I see a potential design flaw here! Killing a process when a file reaches a certain size or uptime does not make much sense, unless you can justify it with some major requirement, or maybe I didn't understand well...

TMBAWTDI! (There MUST Be Another Way To Do It!). What about this metacode: 

sub writer_function {
    if((time - $^T <= $max_uptime) && ($output_size <= $max_size)) {
        #
        # Normal processing here
        #
        $output_size += $size_written;
    } else {
        #
        # Cleanup, then exit
        #
    }
}

[download]

Sounds good?

-- TMTOWTDI

In reply to Re: signal handler in referenced subroutine by trantor
in thread signal handler in referenced subroutine by aijin

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.