[syslog-ng]Logging not matched to filters

[Amodiovalerio Verde]

Try reading http://www.balabit.com/products/syslog_ng/reference/logpath.h=
tml

You can use a log statement with the fallback flag to achieve what=
 you need.

i.e.

source ext { tcp(port(514) max-connections(1024)); =
udp(port(514));};
...your destination statements...
destination unmatch=
ed { file("/var/log/unmatched");};
...your log statements...
log { sour=
ce(ext);destination(unmatched);flags(fallback);};

The last log stateme=
nts will log all 'unmatched by a previous rule' to the file /var/log/unma=
tched.

Hope it helps.


Amodiovalerio [Hypo] Verde


---------- =
Initial Header -----------

>From      : syslog-ng-admin@lists.balabit.h=
u
To          : syslog-ng@lists.balabit.hu
Cc          : 
Date      : =
Mon, 23 Feb 2004 14:27:52 +0100
Subject : [syslog-ng]Logging not matched=
 to filters

> Hi
> 
> I have a lot of filters and they log fine.
> =

> I was wounding if it possible to make a logging that matches the rest=
, 
> that isn't caught in a filter.
> So that if syslog-ng receives a l=
og and it doesn't match any of the 
> filters, it will log it into a fil=
e.
> 
> That way i don't miss a logging from a device, it would simple =
be in this 
> separate file.
> 
> - Henning
> _______________________=
________________________
> syslog-ng maillist  -  syslog-ng@lists.balabi=
t.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Frequently=
 asked questions at http://www.campin.net/syslog-ng/faq.html
> 
>