https://bugzilla.balabit.com/show_bug.cgi?id=123 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |FIXED Status|NEW |RESOLVED --- Comment #1 from Balazs Scheidler <bazsi@balabit.hu> 2011-06-10 12:03:23 --- Thanks for your report. Please note that this is not an official support channel for the PE version. If you want that, you'll need to file a ticket to BOSS. But since I happen to know what the root cause of your problem is, I'm answering your question. The performance improvements that went into PE 4.0 (and later OSE 3.3) broke the handling of messages with a zero priority value. I've forwarded the bug to the syslog-ng PE team, they'll include the fix in an upcoming maintenance release. If you would like something earlier than that, please contact the support team, they can provide engineering releases, and please reference this ticket in your report. This patch in the OSE version fixes it: commit 22c2204c2b664f5017ab50565019513eff611d5d Author: Balazs Scheidler <bazsi@balabit.hu> Date: Fri Jun 10 11:58:09 2011 +0200 logwriter: fixed the formatting of messages with priorities set to 0 If the priority value of a message is 0 (e.g. kern.debug), syslog-ng will emit it as an empty string, instead of zero. This patch fixes that. Signed-off-by: Balazs Scheidler <bazsi@balabit.hu> -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.