running the config check on a subset of the config is likely to run into grief,
run it on the top level config file and it will check the included files.
It's also useful to create a combind file. If you start rsyslog as
rsyslogd -o /path/to/file
that file will contain rsyslog.conf and all included conf files in the order
that rsyslog see them (rsyslog combines all the files, and then starts parsing
them)
having actions in a included config file when you have the module load in the
master file will mean that if you try to check the included file as if it was
the entire config, you will get errors. I think that's what's happening here.
David Lang
_______________________________________________
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.
