log line processed after flags(final)
Are there any known situations where the use of flags(final) would still allow the processing of a matched line by log statements which come later in the config? In this case there are three log statements total which a particular line could possibly match; I want it to be processed by the first two statements but not the third. After adding flags(final) to the second log statement, all statements are still being matched.
On Tue, May 16, 2006 at 12:41:14PM -0400, Kevin Lee Phair II wrote:
Are there any known situations where the use of flags(final) would still allow the processing of a matched line by log statements which come later in the config? In this case there are three log statements total which a particular line could possibly match; I want it to be processed by the first two statements but not the third. After adding flags(final) to the second log statement, all statements are still being matched.
Sounds like a bug, what version are you using? -- Nate
From empirical experience, your Exchange admin needs to put down the crack pipe and open a window to disperse the fumes.
Nate Campi wrote:
On Tue, May 16, 2006 at 12:41:14PM -0400, Kevin Lee Phair II wrote:
Are there any known situations where the use of flags(final) would still allow the processing of a matched line by log statements which come later in the config? In this case there are three log statements total which a particular line could possibly match; I want it to be processed by the first two statements but not the third. After adding flags(final) to the second log statement, all statements are still being matched.
Sounds like a bug, what version are you using?
Found the same issue with 1.6.8 and 1.6.10; this is running on a FreeBSD 4.11 machine, installed from ports. I couldn't reproduce the problem with either version (or 1.6.11) installed on a linux box; I have yet to test on another 4.11 box, but should be able to do so tomorrow.
Are there any known situations where the use of flags(final) would still allow the processing of a matched line by log statements which come later in the config? In this case there are three log statements total which a particular line could possibly match; I want it to be processed by the first two statements but not the third. After adding flags(final) to the second log statement, all statements are still being matched.
Sounds like a bug, what version are you using?
Found the same issue with 1.6.8 and 1.6.10; this is running on a FreeBSD 4.11 machine, installed from ports. I couldn't reproduce the problem with either version (or 1.6.11) installed on a linux box; I have yet to test on another 4.11 box, but should be able to do so tomorrow.
For the record, this was a case of the same log message being sent twice, just different enough to skip by the 'final' log line, but similar enough for a later log line and my eye to not notice the difference.
participants (2)
-
Kevin Lee Phair II
-
Nate Campi