Ah, a discerning question.

Well, when the equipment was running our softswitch code,
a number of processes would be launched and design was very
picky about what was running on the system with their
software. So we needed to sense an uptick in resource use
and shut down processes. This way, when errors popped
up, they wouldn't have to worry if SETI@Home were somehow
to blame.

Unfortunately, when problems did pop up, they did a ps and
saw "setirunner". In other words, we unfortunately named
the script poorly, and it was easily picked out. We should
have named it something unobtrusive... something vaguely
UNIX-system-like. Ah, well.

Rob

In reply to Re: Re: Perl ran SETI@Home for us. by rje
in thread Perl ran SETI@Home for us. by rje

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.