<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap:break-word"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div> <br> <div id="bloop_sign_1473523428423345920" class="bloop_sign"></div> <br><p class="airmail_on">On September 10, 2016 at 10:07:42, Brian (<a href="mailto:bnmille@gmail.com">bnmille@gmail.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>
<title></title>
<p dir="ltr">Syslog-ng has an option to stop processing a message,
if it matches a given rule. You can send the log message to a
file, and then stop processing it (so it will not be written
to any more files). I don't recall the correct syntax,
but it's in the man pages. Then just put the rule for
/var/log/messages at the end of your config file. </p>
<p dir="ltr">I use the stop rule processing to send junk I never
want see to /dev/null. Works well.</p></div></div></span></blockquote><div>Ah, 'log path flags'[1] might be exactly what I need -- probably flags(fallback) on the /var/log/messages log{} block. Somehow I missed this.</div><div><br></div><div>thanks!</div><div><br></div><div>[1] <a href="https://www.balabit.com/documents/syslog-ng-ose-latest-guides/en/syslog-ng-ose-guide-admin/html/reference-logflags.html">https://www.balabit.com/documents/syslog-ng-ose-latest-guides/en/syslog-ng-ose-guide-admin/html/reference-logflags.html</a></div></body></html>