syslog-ng config and problems
I've tried to set up a looging av messages from amavis-new into a separate file, but that fle doesn't get created at all. Can someone please advice? syslog-ng.conf: filter f_mailscan { level(scan) and facility(mail); }; destination mailscan { file("/var/log/mail.scan"); }; log { source(src); filter(f_mailscan); destination(mailscan); }; amavis.conf: $log_level = 6; $LOGFILE = undef; $DO_SYSLOG = 1; $SYSLOG_LEVEL = 'mail.scan'; -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
syslog-ng.conf:
filter f_mailscan { level(scan) and facility(mail); };
destination mailscan { file("/var/log/mail.scan"); }; log { source(src); filter(f_mailscan); destination(mailscan); };
amavis.conf:
$log_level = 6; $LOGFILE = undef; $DO_SYSLOG = 1; $SYSLOG_LEVEL = 'mail.scan';
There is no defined syslog level 'scan'. /Per Jessen, Zürich
Per Jessen wrote:
Anders Norrbring wrote:
syslog-ng.conf:
filter f_mailscan { level(scan) and facility(mail); };
destination mailscan { file("/var/log/mail.scan"); }; log { source(src); filter(f_mailscan); destination(mailscan); };
amavis.conf:
$log_level = 6; $LOGFILE = undef; $DO_SYSLOG = 1; $SYSLOG_LEVEL = 'mail.scan';
There is no defined syslog level 'scan'.
/Per Jessen, Zürich
I believe that you also need to edit, not syslog-ng.conf, but syslog-ng.conf.in and afterwards run SuSEconfig.
ken wrote:
I believe that you also need to edit, not syslog-ng.conf, but syslog-ng.conf.in and afterwards run SuSEconfig.
Personally I just edit syslog-ng.conf. I think you can tell YaST to keep away from syslog-ng.conf by editing some parameter in /etc/sysconfig/syslog. /Per Jessen, Zürich
ken skrev:
Per Jessen wrote:
Anders Norrbring wrote:
syslog-ng.conf:
filter f_mailscan { level(scan) and facility(mail); };
destination mailscan { file("/var/log/mail.scan"); }; log { source(src); filter(f_mailscan); destination(mailscan); };
amavis.conf:
$log_level = 6; $LOGFILE = undef; $DO_SYSLOG = 1; $SYSLOG_LEVEL = 'mail.scan';
There is no defined syslog level 'scan'.
/Per Jessen, Zürich
I believe that you also need to edit, not syslog-ng.conf, but syslog-ng.conf.in and afterwards run SuSEconfig.
Yep, it was the .in file I edited, and then ran SuSEconfig, but still it doesn't work as I expected. However, if Per is right that level "scan" cannot be defined, that's the best explanation... I just tested, without checking any syslog specs, I was under the impression that I could use just anything, and tell the program to use it.. In this case tell Amavis-new to use "mail.scan", but apparently it doesn't work that way. -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
However, if Per is right that level "scan" cannot be defined, that's the best explanation... I just tested, without checking any syslog specs, I was under the impression that I could use just anything, and tell the program to use it.. In this case tell Amavis-new to use "mail.scan", but apparently it doesn't work that way.
Check "man syslog" to see the list of facilities and levels available. /Per Jessen, Zürich
participants (3)
-
Anders Norrbring -
ken -
Per Jessen