Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
The FIFO idea seems to be the best solution for me here. I can point my application to write to a FIFO pipe, and just disregard all lines I would have previously tried to remove. As far as the log rotation; it seems as though it would be as simple as a 'real-time' rotation. Meaning I would base the logfile output on the time/date stamp prefixing each of the incoming lines. Then create new files on the fly based on those metrics. Would an idea like this be the best solution for my problem?

cheers, Ev

Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.

In reply to Re^3: removing lines from a file by ministry
in thread removing lines from a file by ministry

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.