I've found that when we centralized our logs using Sys::Syslog, that errors are not logged.
Consider the following line if $RxString is not defined.
$self->log(3, $self->log_time() . " $$: client said '$RxString'");

When the Net::Server log file is an actual file then the error will be recorded into the log file. But now with Syslog, the errors are sent to the console, and not saved.

I've tried adding something like: open (STDERR, ">>stdout_stderr_log.txt");
but the errors are not being logged.

Thanks for any help you can give.
Aaron

In reply to Net::Server and Sys:Syslog and STDERR by alager

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.