matija,
I debated on mentioning fatalsToBrowser as well. The reason why I suggested carpout extends beyond redirecting errors to another readable log. It is suggested to be put inside a BEGIN block. This allows seeing compile time errors which would normally otherwise be inaccessible. It also allows you to see errors that happen when some other user is accessing it. It helps tracking down problems to have your very own web log when your provider doesn't give you access.

I should have been complete however so thanks for filling in the blanks.

Cheers - L~R

In reply to Re: Re: [slightly OT] Getting errors and bypassing apache error log by Limbic~Region
in thread [slightly OT] Getting errors and bypassing apache error log by Anonymous Monk

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.