in reply to Net::Server and Sys:Syslog and STDERR

As logging to the console is the default fallback behavior when all other attempts to connect to the syslog daemon have failed, I suppose this is exactly what's happening in your case — the order of modes tried is native, tcp, udp, unix, pipe, stream, console, unless you've changed them with setlogsock().

Unfortunately, it's hard to tell why, from here.  Are there any warnings from openlog() etc.?

Replies are listed 'Best First'.
Re^2: Net::Server and Sys:Syslog and STDERR
by alager (Acolyte) on Mar 16, 2010 at 20:29 UTC
    There are no errors reported on STDERR from openlog().
    I would agree with your assessment except that the rest of the messages are continuing to be logged to syslog, as they are supposed to.
    It seems, to me, like perl runtime errors are being directed to the console directly.
[reply]
[d/l]

In Section Seekers of Perl Wisdom