:( Sadly I don't think I can wrangle FIFO's to my needs. I read the File::Tail docs (why does it need Time::HiRes?) , which would be cool for a daemon type execution, but hoping I was to only run this script at intervals.
Closer inspection of Perl InANutShell led me to this...
use strict;
open ( COUNT , '<counter');
my $whence = scalar <COUNT>;
chomp $whence;
close COUNT;
open ( FH , "<logfile" );
# scram to position we wrote last to 'counter'
seek FH, $whence , 0;
my $line = scalar <FH>;
print $line;
my $count = tell FH;
open ( COUNT , '>counter' );
print COUNT $count;
close COUNT;
Which exhibits the behaviour(s) that I believe are needed, in this test case, the script prints the next single line from 'logfile' and exits - saving it's position in logfile to 'counter'. OK so I had to seed counter with '0' first!!
This is destined to run on rh7.3, perl5.6.1 - what scares me most is how squid will behave with another
process reading from the logfile it's writing too.
-
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.
|