Its interesting, so I did my part of checking. see the below code 
perl -e 'BEGIN{close(STDERR)};open FH,">log"; die 'testing';'

[download]
in begin, the STDERR is closed, so no more STDERR(fd 2)
but when 'open FH' is seen, the kernel is trying to allocate the unused file descriptor from starting from 0, now 2 is free, so it is allocated.
when the die executes, it might be a problem with die, it might be programmed to write to fd 2 always, regardless of pointing to STDERR or any other file.
after this code, you can expect the error to be logged in file 'log'.
'perldoc -f die' has no clues on this, it says that 'die prints to STDERR'
(assuming it is always fd 2) Interesting...

In reply to Re: Log message in Die handler by targetsmart
in thread Log message in Die handler by lakshmananindia

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.