thats the output format i'm looking for, just that the data is coming from a logfile.
the script takes a URI from STDIN and parses the file based upon the fields of each line. so if i typed in:
/profileQuery
i get these results:
URI Date Seconds Fil
+e Size
----------------- --------------------- ------- ---
+------
/profileQuery [06/Apr/2004:13:40:36 0
+893
URI Date Seconds Fil
+e Size
----------------- --------------------- ------- ---
+------
/profileQuery [06/Apr/2004:13:41:12 0
+867
URI Date Seconds Fil
+e Size
----------------- --------------------- ------- ---
+------
/profileQuery [06/Apr/2004:13:41:23 0
+883
while that is ok if there are just a few entries for that URI in the log, not so much if there are several hundred. i found some documentation for the field specifiers.. but those were for Perl 6 and didnt work.
here is a snip of the code that looks at the log fields
while(<DB>) {
$Recs = $_;
chomp($Recs);
($IP, $Host, $Dash, $Date, $TZ, $Method, $URL, $Pro, $Status, $Tim
+e, $Size)
=
split(' ', $Recs);
if($URL eq $SearchFor) {
$SuccessCount = $SuccessCount + 1;
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.