[syslog-ng] question on parsed syslog-ng config files and command line options

Jim Hendrick jrhendri at roadrunner.com
Sat Jul 27 17:59:57 CEST 2013


Sent from my Verizon Wireless 4G LTE Smartphone

-------- Original message --------
From: Balazs Scheidler <bazsi77 at gmail.com> 
Date: 07/26/2013  5:35 PM  (GMT-05:00) 
To: Syslog-ng users' and developers' mailing list <syslog-ng at lists.balabit.hu> 
Subject: Re: [syslog-ng] question on parsed syslog-ng config files and command line options 

Not a perfect name, and should probably exit after having done its work.

On Jul 26, 2013 9:46 PM, <jrhendri at roadrunner.com> wrote:

  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.



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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20130727/3dc3bd74/attachment.htm 

More information about the syslog-ng mailing list