On Wed, 20 Feb 2013, Nathan Stratton Treadway wrote:
I'm trying out the rsyslog 7.3.6-0adiscon1 package installed from the
http://ubuntu.adiscon.com/v7-devel/ repository, and I seem to be running
into strange behavior in the processing order for actions and filters
defined in "included" configuration files.
After some investigation (including switching from ~ to STOP, and
from a property-based filter to a ReinerScript filter, etc.), I
discovered that the issue seems to be that the rules from each
newly-parsed config file are added to the top of the ruleset list,
rather than the bottom. (So the rules show up in the expected order
within each config file, but the "blocks" of rules appear in the wrong
order.)
Has anyone else noticed this problem? (I did search around for any
previous discussion of the topic, but wasn't able to find anything....)
My understanding is that the order of multiple include files has always been
undefined. you should not rely on interaction between different files that are
included to always be in a particular order, either amoung the files or in
relation to entries in the main file.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
