Octavian,
I do not see how this is possible without modifying the original script at least a little. When you use IO::Tee, you will be able to tie both the LOG and STDOUT to the same filehandle, so that wherever there is a print statement - it will print in both places. By setting auto-flush ($|), you will see events in the log as they happen (or pretty close). The script you write will have to use File::Tail to constantly be checking the bottom of the log looking for a specific event, which will trigger a desired action - such as email/page.

I am not sure how to help beyond this without seeing the code of the original script, some sample output, and what "events" would like a trigger action.

Cheers - L~R

In reply to Re: Re: Re: Re: reading output from another script by Limbic~Region
in thread reading output from another script by Octavian

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.