[
http://jira.qos.ch/browse/LBCLASSIC-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12081#action_12081
]
Ralph Goers commented on LBCLASSIC-146:
---------------------------------------
There are two variations on the syslog specification. RFC 3164 is the original
'BSD' syslog spec and can be found at http://tools.ietf.org/html/rfc3164. It
explicitly states that only printable characters and spaces are allowed.
RFC 5424 is the new syslog spec and can be found at
http://tools.ietf.org/html/rfc5424. This specification is much more extensive.
It specifies this about the message portion:
"The syslog application SHOULD avoid octet values below 32 (the traditional
US-ASCII control character range except DEL). These values are legal, but a
syslog application MAY modify these characters upon reception. For example, it
might change them into an escape sequence (e.g., value 0 may be changed to
"\0"). A syslog application SHOULD NOT modify any other octet values."
Logback does not support RFC 5424.
> SysLog Appender and Line Breaks = :(
> --------------------------------------
>
> Key: LBCLASSIC-146
> URL: http://jira.qos.ch/browse/LBCLASSIC-146
> Project: logback-classic
> Issue Type: Bug
> Components: appender
> Environment: Debian 4 Etch, 64 Bit (most likely all enviroments)
> Reporter: Ingo Siebert
> Assignee: Logback dev list
>
> I'm using the SysLog appender and it works well.
> But I've problems with line breaks, especially for exceptions. Every strack
> trace line is written as new SysLog-Entry. Example:
> Aug 11 20:25:21 192.168.33.11 app2-cas org.osgi.framework.BundleException:
> The bundle class path entry "patch.jar"..."
> Aug 11 20:25:21 192.168.33.11 app2-cas ^Iat
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassPathEntry(ClasspathManager.java:168)
> Aug 11 20:25:21 192.168.33.11 app2-cas ^Iat
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.buildClasspath(ClasspathManager.java:145)
> Aug 11 20:25:21 192.168.33.11 app2-cas ^Iat
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.initialize(ClasspathManager.java:79)
> ...
> That's quire annoying if you want to filter or highlight entries.
> I think it's major, because there isn't a good workaround to filter/highlight
> syslog files.
> I'm using Logback 0.9.13, but I thinks it still exists in the trunk.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
