Bug 13464 - Support RFC5424-style syslog
Summary: Support RFC5424-style syslog
Alias: None
Product: glibc
Classification: Unclassified
Component: libc (show other bugs)
Version: unspecified
: P2 enhancement
Target Milestone: ---
Assignee: Ulrich Drepper
Depends on:
Reported: 2011-12-01 19:47 UTC by Tim B
Modified: 2014-06-27 11:32 UTC (History)
2 users (show)

See Also:
Last reconfirmed:
fweimer: security-


Note You need to log in before you can comment on or make changes to this bug.
Description Tim B 2011-12-01 19:47:40 UTC
Since RFC 5424, the IETF have defined syslog's wire encoding and format. However the syslog library calls don't support the extended features (including subsecond timestamps as per bug #11715).

Hence this enhancement request.

Other new features that aren't yet available through libc calls are arbitrary STRUCTURED-DATA and the MSGID element.

I don't know if making these changes would mean a new library call, but I suspect it might.
Comment 1 Tim B 2011-12-04 17:29:14 UTC
NetBSD has introduced a new library call, syslogp()

See eg http://www.daemon-systems.org/man/syslogp.3.html
Comment 2 Ulrich Drepper 2011-12-18 01:45:10 UTC
The only reason syslog() as it is exists in libc is because of history.  There is no reason whatsoever to have any new version added to glibc.  Just provide a standalone version.  Just add a library to the syslogd implementation.  Coordination is likely in any case needed and this way there are no problems.
Comment 3 Tim B 2011-12-18 16:40:09 UTC
The worry about having a separate library is to do with standardisation: if there are rival libraries, then applications will adopt one or the other and the daemon that listens to all this won't know what to accept.

If glibc isn't the right place to do this standardisation, where is?