If I have some log paths, then a log path using the fallback flag, then some more log paths... will that path with the fallback flag not capture message that the log paths after it capture? For example, can I do the following: log { source(src); filter(filt_a); desintation(dest_a); }; log { source(src); destination(dest_b); flags(fallback); }; log { source(src); filter(filt_b); destination(dest_c); }; Will messages not filtered by filt_a be captured by the second log path and then again by the third? If not, is there any way to do this? My understanding was the old filter(DEFAULT) would behave like this, but flags(fallback) would not. Can the same effect still be accomplished? TIA, Andrew
On Tue, 2004-01-27 at 00:54, Andrew Culver wrote:
If I have some log paths, then a log path using the fallback flag, then some more log paths... will that path with the fallback flag not capture message that the log paths after it capture? For example, can I do the following:
log { source(src); filter(filt_a); desintation(dest_a); }; log { source(src); destination(dest_b); flags(fallback); }; log { source(src); filter(filt_b); destination(dest_c); };
Will messages not filtered by filt_a be captured by the second log path and then again by the third? If not, is there any way to do this? My understanding was the old filter(DEFAULT) would behave like this, but flags(fallback) would not. Can the same effect still be accomplished?
fallback destinations are processed after all other log paths were processed and none of them matched. you can have several fallback log paths, so the solution is to specify flags(fallback) for all log paths after your DEFAULT one. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
Andrew Culver
-
Balazs Scheidler