On Thu, 2010-01-28 at 17:41 +0000, Philip M. Gollucci wrote: > > I just tried it out. I got the following error message: > > > > === > > 2010-01-28T18:33:41.635158+01:00 rgf12 rsyslogd-2051: syntax error in > > expression [try http://www.rsyslog.com/e/2051 ] > > 2010-01-28T18:33:41.635413+01:00 rgf12 rsyslogd: the last error occured > > in /home/rger/proj/rsyslog/rg.conf, line 10:"if $facility == 1 && > > $priority == 7 then ~" > > 2010-01-28T18:33:41.635477+01:00 rgf12 rsyslogd: warning: selector line > > without actions will be discarded > > 2010-01-28T18:33:41.636170+01:00 rgf12 rsyslogd-2124: CONFIG ERROR: > > could not interpret master config file > > '/home/rger/proj/rsyslog/rg.conf'. [try http://www.rsyslog.com/e/2124 ] > > well thats useful at least. I wonder why I don't see it. >
well, I guess that's the ole question on alternatives to using the logging system itself to log error messages... The mailing list has a couple of posts on this, one I thread I think in December or early this month. I guess you did not capture syslog messages themselves. Rainer > > The syntax error is &&, you need to use "and". Also, the property names > > were incorrect. So the correct line would have been: > > > > if $syslogfacility == 1 and $syslogseverity == 7 then ~ > d'oh > > > > > While I have verified that this line works, you are far better of > > (performance-wise) with the traditional priority filter that you now > > use. > Yes! > > Thx! > > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
