okay, i won't give it all away, but here's a good start.

while(<FILE>) {
    my @x = split /,|\^`/;
    next unless ($x[4] =~ /560/);  #we only want the files with 560
    print join("\n",@x), "\n"; # debugging print line - remove in prod
+uction
    unless($x[16] =~ /Primary User Name:    CISERFS1/) { #only match t
+his case
        print OUTPUT "$x[1] $x[2] $x[12] $x[16] \n"; # or whatever
    } # unless
} # while

[download]
by the way, you should get a login, so we know who you are when you come back!

~Particle

Update: i guess i forgot about the '\' parsing, but i'm not sure just what you want to do. you can split on /\\/, and return the fields you want, put together with join "\\", much like i did in the debug print statement.

In reply to Re: Re: Re: parse a log file by particle
in thread parse a log file 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.