I assume that you want to preserve the older entries and just overwrite existing ones. The relevent question in this case is whether each line or log block is of fixed size.

For example, if you structure your log messages to be, say, 384 bytes or less (any size will do), then open your log in r/w mode. If the file is of the correct size, position the pointer at the beginning of the file and begin writing your standard blocks. If the file is not yet of the correct size, position the file pointer at the end of the file and keep adding.

The only thing you need is a MAXSZ, CURRSZ and BLOCKSZ variable to track location.

I'm sure there are other ways but this was the first one that came to mind.

PJ
use strict; use warnings; use diagnostics;

In reply to Re: truncate a file from top by periapt
in thread truncate a file from top by SiLiK

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.