I'm working on a script that runs a shell command that may occassionally run awry and generate huge amounts of looping data. What I'm trying to figure out is how to monitor the size of the data generated and kill the process if it hits above x bytes.

The problem is that this command doesn't feed back the data as it generates it, but waits until the end and sends it all back in a hash. So I'm taking a look at Proc::ProcessTable::Process. It has a command size which returns the process' virtual memory in bytes.

Is this what I need? I'm not all that knowledgable with the inner workings of these machines. There's another command called rss which returns the resident set size, but I have no idea what that is, and the virtual memory command seems to be more likely the right choice.

-aijin


In reply to using Proc::ProcessTable::Process 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.