I'm making assumptions but I guess you mean that errors and warnings generated by warn or die go to STDERR whereas normal messages generated by a plain print without a filehandle go to STDOUT. On a *nix system you can run a script from the shell (Bourne, Korn, Bash) like this

script_name > output_file 2>&1

[download]

which directs STDOUT of the script into the "output_file" and also directs STDERR (file descriptor 2) into STDOUT (file descriptor 1). That way, you can get both STDOUT and STDERR into one file. I'm not sure what you would do in a MS Windows environment, perhaps other Monks can tell you (and me) what to do there.

I hope this is of use.

Cheers,

JohnGG

In reply to Re: execution log by johngg
in thread execution log by yburge

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.