[Bug 220] New: Version 3. 4 logical configuration incompatible with previous versions
https://bugzilla.balabit.com/show_bug.cgi?id=220 Summary: Version 3.4 logical configuration incompatible with previous versions Product: syslog-ng Version: 3.4.x Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: erempel@uvic.ca Type of the Report: --- Estimated Hours: 0.0 In version 3.3 the top level configuration structure treated all log statements as if they were inside a single block. If there was a log statement with a flags(final) then no other log statements were processed. This allowed @include statements to include snippets that included logs statements with flags(final). In version 3.4 the top level configuration structure treats all log statements independently. If there was a log statement with a flags(final) it only affects processing within that log statement and processing does continue with then next log statement. Including files with log statements and flags(final) can'r really be done and the @include can not be used inside of log statements. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=220 --- Comment #1 from Balazs Scheidler <bazsi@balabit.hu> 2013-02-09 06:30:03 --- this sounds like a bug to me, certainly wasn't intended. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=220 --- Comment #2 from Evan Rempel <erempel@uvic.ca> 2013-02-28 05:41:09 --- Is there any progress on this. It is preventing us from deploying 3.4 in our environment. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=220 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |algernon@balabit.hu AssignedTo|bazsi@balabit.hu |algernon@balabit.hu -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=220 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |3.4.2 Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=220 --- Comment #3 from Gergely Nagy <algernon@balabit.hu> 2013-02-28 10:34:14 --- (In reply to comment #2)
Is there any progress on this. It is preventing us from deploying 3.4 in our environment.
Not yet, but it is the top of my priority list at the moment, and I expect to have a fix by tomorrow night. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=220 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bazsi@balabit.hu --- Comment #4 from Balazs Scheidler <bazsi@balabit.hu> 2013-02-28 11:42:33 --- I was faster :) The fix is available on the f/fix-branch-property-propagation, in the 3.4 tree on github. Since test coverage is lacking in this area, I'd appreciate some 3rd party testing on the code, meanwhile I'm thinking on how to automate these testcases, as there are a lot of those, and validating the LogExprNode compilation is not very simple. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=220 --- Comment #5 from Balazs Scheidler <bazsi@balabit.hu> 2013-02-28 12:08:49 --- After a number of manual test cases, and running all the automatic tests I have revealed no bugs. The original issue affected the use of the "fallback" flag too, which should be fixed. A minor change was made in the handling of the flow-control flag, but I concentrated my testing on that and seems to be fine. If anyone could give this a spin, it'd be nice to concentrate on the handling of these flags in your own use-case. Thanks in advance. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=220 --- Comment #6 from Evan Rempel <erempel@uvic.ca> 2013-02-28 20:48:47 --- I applied those three commits/patches and my included destinations now honor the final flag. thanks. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=220 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |FIXED Status|ASSIGNED |RESOLVED --- Comment #7 from Gergely Nagy <algernon@balabit.hu> 2013-03-01 09:41:35 --- Merged Bazsi's patches to master, closing the issue. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
bugzilla＠bugzilla.balabit.com