you could have syslog-ng log messages from itself (source internal) to a separate file and use something like logwatch (or other log monitoring programs) to watch for errors in the file and report issues. On Thu, 2007-05-31 at 00:01 +0000, Bryan Henderson wrote:
My syslog-ng got into an infinite loop when it didn't have permission to write to a file destination. It tried to log to that same destination the fact that it failed to log.
Is there a recommended way to configure syslog-ng to avoid this? Maybe I could route messages from Syslog itself to some relatively reliable destination or just turn them off?
If not, what would be a good enhancement to the program to avoid loops?
I had the problem with syslog-ng 2.0.2.
-- Hiren Patel ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail and its contents are subject to the Telkom SA Limited e-mail legal notice available at http://www.telkom.co.za/TelkomEMailLegalNotice.PDF ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~