As hossman points out a __DIE__ handler would be helpful since I noticed you do have some die's but you are only sending the message to STDERR not to your log files.

It also looks like you started to use syslogd, but stopped to use your own logfiles. I would recommend going to syslogd and you'll be able to get away from some of the pitfalls with straight logfiles(e.g. multiple instances of you program, disk space, permissions, not able to remotely monitor without NFS). There are some CPAN modules for a OO interface to syslogd: Net::Syslog Tie::Syslog Unix::Syslog



grep
grep> cd /pub
grep> more beer

In reply to Re: debugging strategy? by grep
in thread debugging strategy? by mbr

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.