You don't have to close the filehandle to commit its output to disk. First, make sure you're flushing to the disk on every write, either by setting $| or with IO::Handle::flush. Then, to ask the OS to actually write the data to disk, use IO::Handle::sync. This may slow you down significantly, simply because disks are slow compared to memory, but the hit is probably less than a close/open.

It's up to you to find the right tradeoff between the speed of your code and how much data is lost in the event of an unclean shutdown.

One other thought: you can install all the signal handlers you want, but until there's a $SIG{TRIPPED_OVER_POWER_CORD}, that won't be foolproof.

In reply to Re: How do I dump data to file on hard exit? by sgifford
in thread How do I dump data to file on hard exit? by starbuck

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.