With the shell tail function, you will hit the current EOF. You cannot read past the EOF. After awhile (suitable time delay for your application), you have to do another tail in order to see additional lines that have been added. This is normal.

Without knowing much about your particular problem (one example line is not much to go on), sometimes in this situation, all that is needed is to monitor the size of the file and just verify that it continues to grow. my $size = -s "logfile";. Of course that won't work if the program continues to grow the file in spite of being in some kind of error mode.

Update: The system tail command should be adequate for what you need. I presume that you are only doing this once per 30-60 seconds? Or maybe even less often? Also consider whether or not a simple line "eq" string comparison is adequate (current last line not identical to the last line at the last time that we checked). It could be that you don't even need a regex? Again without more details about this log file, it is impossible to say. If you show evidence to reject my simple "check file size" suggestion, then along the way you will provide us with enough data to write a proper regex for you.


In reply to Re^5: Searching a string in running file by Marshall
in thread Searching a string in running file by t-rex

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.