Bazsi, thank you, this is the info I needed. regards, Siem -----Oorspronkelijk bericht----- Van: syslog-ng-bounces@lists.balabit.hu namens Balazs Scheidler Verzonden: ma 6-7-2009 8:58 Aan: Syslog-ng users' and developers' mailing list CC: documentation@balabit.com Onderwerp: Re: [syslog-ng] Unable to set PRIORITY and LEVEL in rewrite On Fri, 2009-07-03 at 22:11 +0200, Siem Korteweg wrote:
Hi,
thank you for your reaction and hint. Where are these options documented, I cannot find them in de admin manual.
as it seems the docs has not yet been updated. you can find more information about this feature in the mailing list archives starting at this thread: https://lists.balabit.hu/pipermail/syslog-ng/2009-March/012638.html and this: https://lists.balabit.hu/pipermail/syslog-ng/2009-April/012858.html The way it works is as follows: source aaa { file("/var/log/apache/error.log" default-facility(daemon) default-priority(error)); }; This means that all lines that do not begin with a syslog header (<NNN> where NNN is the syslog PRI value), will get "daemon.error" instead of the earlier hard-coded "user.notice". -- Bazsi _____________________________________________________________________________ _ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html