Sounds to me like you need logcheck. It's a shell script, usually set up by the admin as an hourly cron job, but also workable in your home space if you have permission to access the logs. it might save you some work.

Failing that, here's the bit that will read the file and record anything bad it finds:

my $logfile = '/full/path/to/logfile';
my $badnews;
open (LF, "<$logfile") or die ("open $logfile failed: $!);
flock (LF,1) or die ("flock $logfile failed: $!");    
while (<LF>) {
    $badnews .= $_ if (m/bad news/i); # some work needed
}
close(LF) or die ("close $logfile failed: $!);

if ($badnews) {
    # do something
}

[download]

Which just leaves you to write the regex that will spot bad news in the file, and a sub to send you $badnews in an email message if it finds any.

You should also replace the or die() instructions with something that will send you another sort of message if reading the logfile fails.

Bear in mind that there are issues with constantly incremented files: when perl opens the file it will remember the length of it and read only that far unless you resest the EOF flag. It probably doesn't matter, but the cookbook has more information if you need it.

Hope this helps.

In reply to Re: reading of log files by thpfft
in thread reading of log files by Anonymous Monk

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.