question on parsed syslog-ng config files and command line options
Hi, I remember seeing (somewhere...) a command line option for syslog-ng that created an output file that was essentially the "resulting configuration" after all #include files were processed. I am trying to debug a problem with message parsing, and my filters are maintained in separate files. I was hoping I could remember this option so I could see what syslog-ng "thought" the resultant config was but (neither myself nor google) can remember it. essentially it expands all the include files "inline" and produces one output file. Help? Thanks, Jim
--preprocess-into Not a perfect name, and should probably exit after having done its work. On Jul 26, 2013 9:46 PM, <jrhendri@roadrunner.com> wrote:
Hi,
I remember seeing (somewhere...) a command line option for syslog-ng that created an output file that was essentially the "resulting configuration" after all #include files were processed.
I am trying to debug a problem with message parsing, and my filters are maintained in separate files.
I was hoping I could remember this option so I could see what syslog-ng "thought" the resultant config was but (neither myself nor google) can remember it.
essentially it expands all the include files "inline" and produces one output file.
Help?
Thanks, Jim
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
participants (2)
-
Balazs Scheidler
-
jrhendri@roadrunner.com