Hello everyone. Well, I was able to write my script to extract data from my firewall logs. Here it is: 

# START CONFIG
$firewall_log = "/home/jwilliams/firewall.txt";
$my_new_log = "/home/jwilliams/extracted_log";
# END CONFIG

open(FW_LOG, "$firewall_log");
@lines = <FW_LOG>;
close(FW_LOG);

open(MYNEWFILE, ">>$my_new_log");
foreach $line (@lines){
  if($line =~ /kernel Temporarily blocking host/ || $line =~ /blocked/
+){
    print MYNEWFILE $line;
  }
}
close(MYNEWFILE);

exit;

[download]
It does what I want to do, but the log that is generated turns out very ugly and not very clean. Is it possible to somehow clean it up so the log will look nice and neat?

Thanks.

20030410 Edit by Corion: Added CODE tags, indented code

In reply to My first Perl script by tarballed

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.