Bug 502445 - Sys::Syslog can not deal with EMERG level messages
Summary: Sys::Syslog can not deal with EMERG level messages
Keywords:
Status: CLOSED DUPLICATE of bug 454602
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: perl
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Marcela Mašláňová
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-25 10:38 UTC by Lubomir Rintel
Modified: 2009-05-25 13:58 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-25 13:58:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Be able to handle EMERG/LOG_EMERG correctly (396 bytes, text/plain)
2009-05-25 10:38 UTC, Lubomir Rintel
no flags Details
Revised patch, allows LOG_KERN which clashes with EMERG (2.91 KB, text/plain)
2009-05-25 11:25 UTC, Lubomir Rintel
no flags Details

Description Lubomir Rintel 2009-05-25 10:38:21 UTC
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.

Comment 1 Lubomir Rintel 2009-05-25 11:25:41 UTC
Created attachment 345302 [details]
Revised patch, allows LOG_KERN which clashes with EMERG

Comment 2 Marcela Mašláňová 2009-05-25 13:58:52 UTC
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 ***


Note You need to log in before you can comment on or make changes to this bug.