Bugreport: Ver 1.9.5 problems with facility/level filtering
Balazs... I didn't know if you'd seen this (original) thread (I won't repeat all of it here, but did repeat Peter's suggested fix below). I applied this fix, and it did resolve my problems, as it did Peter's. I looked at the latest snapshot, and didn't see this particular change applied, so I figured that I'd ask whether this is something that should be applied(?) Or... Possibly... It's resolved through some other means, or worse (for me) maybe it implies that I've got something else misconfigured, that is actually the root cause of my (and maybe Peter's) problem. If there's any information that you need from me, I'd be happy to supply it. Thanks for your good work and efforts! Marvin -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of pnahas@mrv.com Sent: Friday, September 30, 2005 2:27 PM To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng] Ver 1.9.5 problems with facility/level filtering I too have experienced this problem and decided to investigate the source code. Unless I'm missing something, it appears that 1.9.5 simply does not set the correct variable internally, regardless of configuration. The following patch solved the problem for me: --- /home/pnahas/syslog-ng-1.9.5/src/filter.c 2005-01-05 06:40:50.000000000 -0500 +++ filter.c 2005-09-30 16:23:29.000000000 -0400 @@ -162,6 +162,7 @@ { FilterPri *self = g_new0(FilterPri, 1); + self->valid = facilities; self->super.eval = filter_facility_eval; return &self->super; } @@ -180,6 +181,7 @@ { FilterPri *self = g_new0(FilterPri, 1); + self->valid = levels; self->super.eval = filter_level_eval; return &self->super; } Hope that helps! -Peter Nahas
I didn't know if you'd seen this (original) thread (I won't repeat all of it here, but did repeat Peter's suggested fix below). I applied this fix,
He read the thread and interestingly wrote that he'd applied _a_ fix. So most probably he did not apply Peter's exact patch.
and it did resolve my problems, as it did Peter's. I looked at the latest snapshot, and didn't see this particular change applied, so I figured that I'd ask whether this is something that should be applied(?) Or... Possibly... It's resolved through some other means, or worse (for me) maybe it implies that I've got something else misconfigured, that is actually the root cause of my (and maybe Peter's) problem.
The latest snapshot having the fix is always at most 24 hours later. So you might want to download the latest snapshot again today and verify your findings. I don't have time to do it right now but it would be perfect if you could spare some minutes and try again with the newest snapshot drop. Best regards, Roberto Nibali, ratz -- ------------------------------------------------------------- addr://Kasinostrasse 30, CH-5001 Aarau tel://++41 62 823 9355 http://www.terreactive.com fax://++41 62 823 9356 ------------------------------------------------------------- terreActive AG Wir sichern Ihren Erfolg -------------------------------------------------------------
participants (2)
-
Marvin.Nipper@Stream.com
-
Roberto Nibali