this task can be accomplished with a perl one-liner:

perl -ne"/error|warning/i && print" rc.log

but if you'd like to make it a script, with full error checking, i might do something like:

#!/opt/perl5/bin/perl5.005 -w
use strict;
use warnings;
$|++;

## process each file passed on command line
for my $file ( @ARGV )
{
  ## open the file for reading
  open( RC => "<", $file )
    or die "Can't open $file";

  ## print the program name and current file to be processed
  print "$0: $file\n";

  ## print errors and warnings
  while(<RC>)
  { print if /error|warning/i }
  close RC;
}

[download]

~Particle *accelerates*

In reply to Re: log search by particle
in thread log search by Lhamo_rin

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.