Summary: | Support RFC5424-style syslog | ||
---|---|---|---|
Product: | glibc | Reporter: | Tim B <isoma> |
Component: | libc | Assignee: | Ulrich Drepper <drepper.fsp> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | fweimer, rgerhards |
Priority: | P2 | Flags: | fweimer:
security-
|
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: |
Description
Tim B
2011-12-01 19:47:40 UTC
NetBSD has introduced a new library call, syslogp() See eg http://www.daemon-systems.org/man/syslogp.3.html 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. 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? |