Originally it showed in the log on the client. There is a sequence number in each record that the process watches. If the sequence number was less than the current one, it figured it was a restart. printed to the log what the previous sequence number was, and the current one, and over and over everytime it got to that warning in the log, the sequence number was from the first record in the file.
In my original post I put the logic to watch for a restart so it wouldn't try and stream all that data. that had been processed already. That code in the original post is almost the whole script minus the Socket connection.
First the script receives the last record inserted into the database, creates the file::tail instance, then starts processing the log file and doesn't start streaming records until it gets to last line inserted.
I guess that was a long winded way of saying everything is in the original post of this thread. I am convinced that one of the options I set here
in reply to Re^3: Man, File::Tail is just beating me down!
in thread Man, File::Tail is just beating me down!
has something in it's subroutine that causes a restart when I don't want one. It also looks like he does some sort of seek? Maybe to find where it left off? That would be cool to jump straight to where it left off by tracking the bytes. :)
$file=File::Tail->new(name=>$filename, maxinterval=>5, interval=>1, ta
+il=>-1, ignore_nonexistant => 1, errmode=>\&do_exit);