Be VERY CAREFUL doing this in a production setting. Items in a web server's error log could easily contain very privileged information, including database usernames/passwords, or snippets of code that could contain other sensitive information. Additionally, this opens you up to some cross-site scripting vulnerabilities. I would be very wary of doing something like this on a production server. Remember that the "last few lines" of your error log could easily be output from another script!

If you're just trying to debug your CGI scripts, consider using CGI::Carp to do this. I'd still turn this off on a production site, though.

In reply to Re: Reading the last fews lines of the Apache error log by Fastolfe
in thread Reading the last fews lines of the Apache error log by markjugg

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.