Hi folks - any thoughts re this? I have read the correspondence re "ruleset as a variable". Could not solve my case: my included file might be pulled into the main config file in different locations / sections, under different (legacy syntax) $RuleSet directives. I can't seem to find a good way to have my message filters be included, but always leave the "current" ruleset in effect.
Thanks! rsyslog-users mailing list wrote > Hi folks, > > New to the ML. > I have a config file part (pulled from .../rsyslog.d/) which, due to the > structure of the config process, *might* be pulled in in different parts > of the config file. > > It would be really helpful if I could figure out the currently active > RuleSet when my config code runs. I was looking for $RuleSet as a property > I can query, but that's not available. > > Any other way to do that? > > Thanks in advance for any insight. -- Sent from: http://rsyslog-users.1305293.n2.nabble.com/ _______________________________________________ rsyslog mailing list https://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.
