[syslog-ng] [Bug 238] syslog-protocol: allow NILVALUE for TIMESTAMP as specified in rfc5424
bugzilla at bugzilla.balabit.com
bugzilla at bugzilla.balabit.com
Sat Jun 29 12:26:04 CEST 2013
https://bugzilla.balabit.com/show_bug.cgi?id=238
Balazs Scheidler <bazsi at balabit.hu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |algernon at balabit.hu
--- Comment #1 from Balazs Scheidler <bazsi at balabit.hu> 2013-06-29 12:26:04 ---
I have fixed this with this patch:
commit fd6e77f64cc510b6b45497fca6b53eb8070f90f6
Author: Balazs Scheidler <bazsi at balabit.hu>
Date: Sat Jun 29 12:24:36 2013 +0200
syslog-format: accept RFC5424 NILVALUE in timestamps
RFC5424 states:
In section 6:
TIMESTAMP = NILVALUE / FULL-DATE "T" FULL-TIME
In section 6.2.3
A syslog application MUST use the NILVALUE as TIMESTAMP if the syslog
application is incapable of obtaining system time.
This patch changes syslog-ng to conform to this requirement as it reported
a parse error instead.
Reported-By: Vincent Brillault <spam at lerya.net>
Signed-off-by: Balazs Scheidler <bazsi at balabit.hu>
It is available on the hotfix/3.4/syslogparse-nilvalue-in-dates branch in the syslog-ng 3.4 repository on github.
@Algernon: can you please merge it to master? Thanks.
--
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the syslog-ng
mailing list