I know when I was using a combination of Win32::Gui and Win32::Ole and I would do lots of file crunching/number crunching, opening and closing lots of excel spreadsheets and so-on it seemed like I had memory leaks and general instabilities that I never fully tracked down.

I think that this is the question that you are asking? Is there a problem having a perl script that runs indefinitely, will there be be in pitfals to doing it, memory leaks, zombie processes, etc...? For the task that you are doing my inclination is no, you should be fine, but I do not have nearly the knowledge base or experience as many of the others here. So hopefully someone else can concur, or if any, point out the potential problems.

In reply to Re: Using pipe and reading from the stdin by doowah2004
in thread Using pipe and reading from the stdin by mellin

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.