#2532 assigned defect

Syslog facility 0 (LOG_KERN) is not handled correctly

Reported by: Nick Withers Owned by: Needs Funding
Priority: normal Milestone: Indefinite
Component: network/legacy Version: 4.11
Severity: normal Keywords:
Cc: Blocked By:


Attachments (1)

syslog-ticket_2532.patch (783 bytes) - added by Nick Withers on Jan 18, 2016 at 7:10:40 AM.

Download all attachments as: .zip

Change History (7)

Changed on Jan 18, 2016 at 7:10:40 AM by Nick Withers

Attachment: syslog-ticket_2532.patch added

comment:1 Changed on Jan 18, 2016 at 12:50:59 PM by Gedare Bloom

Does this affect 4.9 and 4.10?

comment:2 Changed on Jan 19, 2016 at 12:54:02 AM by Nick Withers

Firstly, I'd argue 4.9 and 4.10 syslog have bigger problems: https://git.rtems.org/rtems/commit/?id=a32f996b6041ed60aec7ecd23cb750e98ba56e4f

But yes, 4.10 does, as does 4.9

comment:3 Changed on Jan 19, 2016 at 12:58:25 AM by Nick Withers

In my always-humble opinion (:-P), it's a bit of a mess all round, but that's largely because a) the syslog functions in general are broken by design (no provision for error) and thus try to do "strange" things to proceed (e.g., if you don't supply a valid severity, it might try to use the last valid severity, if any, which could be totally wrong) and b) because the intended behaviour isn't well documented anywhere (either in any kind of standard or in RTEMS itself)

comment:4 Changed on Jan 19, 2016 at 4:56:09 AM by Nick Withers

Component: Generalnetworking
Owner: set to norume@…

comment:5 Changed on Jan 26, 2017 at 7:16:00 AM by Sebastian Huber


comment:6 Changed on Feb 15, 2017 at 1:37:51 PM by Sebastian Huber

Milestone: 4.11.2Indefinite
Owner: changed from norume@… to Needs Funding
Status: newassigned
Note: See TracTickets for help on using tickets.