I am not concerned about the server running out of memory therfor ulimit will not help.

What I am concerned about is getting information that my app spent over 8 hours processing and prevent reports like this:

# more runfwrpt-20030829-0230
Out of memory during request for 24 bytes, total sbrk() is 317718640 bytes!
Out of memory during request for 1016 bytes, total sbrk() is 317718640 bytes!
Out of memory during request for 1016 bytes, total sbrk() is 317718640 bytes!


The above isn't a very usefull report...

Even if it only processed half of the files I'd rather have it spit out an error message, and report what it has processed so far.

In reply to Re: Re: Remaining Memory on a system by smellysocks
in thread Remaining Memory on a system by smellysocks

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.