Bug 502445
| Summary: | Sys::Syslog can not deal with EMERG level messages | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Lubomir Rintel <lkundrak> | ||||||
| Component: | perl | Assignee: | Marcela Mašláňová <mmaslano> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE <qe-baseos-auto> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 5.5 | ||||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-05-25 13:58:52 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 345302 [details]
Revised patch, allows LOG_KERN which clashes with EMERG
This was already fixed in #454602. This update should be in RHEL-5.3 update. *** This bug has been marked as a duplicate of bug 454602 *** |
Created attachment 345299 [details] Be able to handle EMERG/LOG_EMERG correctly Version-Release number of selected component (if applicable): perl-5.8.8-15.el5_2.1 Actual results: [root@trunk:~] perl -MSys::Syslog -e 'syslog LOG_EMERG => "boo"' syslog: invalid level/facility: LOG_EMERG at -e line 1 Expected results: 09/05/25 12:25:09 role=?, status=? [root@trunk:~] perl -MSys::Syslog -e 'syslog LOG_EMERG => "boo"' Message from syslogd@trunk at May 25 12:25:16 ... root: boo Additional info: Patch is attached. Fixed upstream. Upstream's new version of the module has the method almost completely rewritten, a similar conditional (permitting log level with numerical value 0) can be spotted there though.