Thanks Nate -- I'm not sure this applies to me though. While yes that catches all specified levels, I was hoping to utilize the fallback flag. My understanding is that the fallback flag takes anything that hasn't been logged up until the log statement in which the fallback flag is in, gets logged to whatever destination you specify. Does the fallback flag do what I want? Also, I've read the descriptions of the "catchall" flag, but I don't fully understand it.. should I be using that instead? Thanks! BTW -- I'm using syslog-ng version 1.6.0rc1 --- nate <syslog-ng@aphroland.org> wrote:
Doug Peterson said:
Any help is greatly appreciated. :)
I do this for one of my syslog-ng clients which forwards to the syslog-ng server through a firewall:
options { long_hostnames(off); sync(0); }; source src { unix-dgram("/dev/log"); unix-dgram("/etc/bind/dev/log"); internal(); }; destination d_tcp { tcp("216.39.174.24" port(24350)); }; filter all { level (debug..emerg); }; log { source(src); filter(all); destination(d_tcp); };
it seems to catch everything ??
__________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com