In that case, your script would print out the results for each
time interval and then go on to evaluate the next lines of
the logfiles, like this:
while(<>) {
$timestring = $_ =~ $some_regexp;
$min = &get_nr_of_mins ($timestring);
if(/start:/) {
/split/ and ++$split;
/filter/ and ++$filter;
}
elsif(/finish:/) {
/split/ and --$split;
/filter/ and --$filter;
}
if($min % $granularity == 0) {
print "$time: $split, $filter\n";
}
}
(note, that this gives you the number of processes at the time
of the last line eaten from the logfile, not an average value for the last interval).
OTOH, if you want to do more sophisticated analysis of the
logfile, this approach might be too simple.
-
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.
|