|Main Archive Page > Month Archives > syslog-ng-users archives|
>From: Balint Kovacs [mailto:firstname.lastname@example.org]
>Sent: Thursday, August 18, 2011 2:35 AM
>when I do something like this, I usually take a different approach, I use a script called from snmptrapd to write the >log message to a socket. If you use something different than /dev/log (e.g. /dev/log.snmp), it's also easier to filter >on the message. I am not sure if SEC has pre-defined rules for traps, but if not, this is probably easier to handle of >you are not using a LOT of traps. If it's just port-security violations and link up/down messages on a moderately >sized network, it should work fine.
Thanks for the configs. I'm guessing that snmptrapd is running in daemon mode. As such, it reads its options from /etc/default/snmpd.
What options do you have set for snmptrapd?
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng