I have a module loaded via PerlModule in the .conf file that exists solely to do some consistency checks and die with a verbose error message if they fail so that startup of apache bails out.

This works great, except that instead of just showing the error message (say, "foo\nbar\nbaz\n") on stderr, it looks like: 

Syntax error on line 64 of /.../httpd.conf:
foo\nbar\nbaz\nCompilation failed in require at (eval 4) line 3.\n

[download]
Is there a better way to do this? I don't mind the "Syntax error"/"Compilation failed" being added so much, but I'd really like to get literal newlines in the error message instead of having them translated to \n's.

In reply to apache2 startup consistency checks by ysth

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.