+++ This bug was initially created as a clone of Bug #949927 +++
Description of problem:
Level LOG_EMERG seems to be not recognized as valid level for syslog calls.
Other levels "LOG_ALERT LOG_CRIT LOG_ERR LOG_WARNING LOG_NOTICE LOG_INFO" were accepted and produced messages. LOG_DEBUG was accepted as valid level too.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. perl -e 'use Sys::Syslog; syslog(LOG_EMERG, "emergency")'
syslog: level must be given at -e line 1.
"emergency" message written
--- Additional comment from RHEL Product and Program Management on 2013-04-09 10:02:47 GMT ---
This bugzilla has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases,
it is also being [proposed|marked] as a blocker for this release.
Please resolve ASAP.
--- Additional comment from Petr Pisar on 2013-04-09 13:08:53 GMT ---
Thanks for the report. It has been fixed in Sys-Syslog-0.31 <http://cpansearch.perl.org/src/SAPER/Sys-Syslog-0.31/Changes> which has not yet been merged into stable perl release.
I will sub-package Sys-Syslog from perl and package latest release from CPAN which contains the fix.
All perl 5.16 releases are affected, F≥18 are affected.
Fixed with perl-5.16.3-269.fc20 and perl-Sys-Syslog-0.32-1.fc20 in F20.
perl-5.16.3-262.fc19, perl-Sys-Syslog-0.32-1.fc19 has been submitted as an update for Fedora 19.
perl-5.16.3-242.fc18, perl-Sys-Syslog-0.32-1.fc18 has been submitted as an update for Fedora 18.
perl-5.16.3-262.fc19, perl-Sys-Syslog-0.32-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 956257 has been marked as a duplicate of this bug. ***
perl-5.16.3-242.fc18, perl-Sys-Syslog-0.32-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.