First, apologies for not having answered earlier.
Two years ago, allank@nbs-inc.com wrote:
Show quoted text> Hi - We've just updated a bunch of systems and we seem to have an
> issue with perl and it's syslog function.
> It doesn't seem to report at the correct levels.
>
> uname -a
> FreeBSD freebsd84-64.rock.nbs 8.4-RELEASE-p4 FreeBSD 8.4-RELEASE-p4
> #0: Mon Sep 9 23:16:13 UTC 2013 root@amd64-
> builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
>
> We also tried it on FreeBSD 9.2-RELEASE and it exhibited the same
> issues.
>
> perl -v
>
> This is perl 5, version 16, subversion 3 (v5.16.3) built for amd64-
> freebsd-thread-multi
>
> We noticed that we were getting console messages from some perl
> scripts and we couldn't figure out why.
>
> What we did to verify this is on our FreeBSD systems. We changed our
> logging to log everything to the /var/log/all.log file and had syslog
> command line arguments set to -vvs so that the level and priorities
> are printed along with the log message. Then we ran the enclosed
> script to see what levels were requested vs what was actually sent to
> the syslog. The script loops though all of the priorities and then
> each facility at that priority.
>
> We also tried it on perl 5.12.4 and everything worked just fine. We
> know there was a re-write of the module in between the versions.
>
> It could also be that we are using the library wrong. I'm not much of
> a perl expert.
This was a bug present in versions 0.29 and 0.30, fixed in version 0.31,
released 2012.08.18:
- [BUGFIX] Level 'emerg' could not be used since v0.29.
- [BUGFIX] Setting a message facility with syslog() was broken
since v0.29 (Noel Butler).
In such a case, upgrading to the latest version, or a previous version,
is usually safe. All released versions can be found on the CPAN or
BackPAN, and can be easily accessed from the "Jump to version" menu
on the MetaCPAN page:
ยป
https://metacpan.org/pod/Sys::Syslog
--
Close the world, txEn eht nepO.
RT for rt.cpan.org