Well, for now I got around it being executed twice by moving the
snmptrapd.conf file to /etc and then specifying the new location when
launching snmptrapd:
/usr/local/sbin/snmptrapd -OS -c /etc/snmptrapd.conf -Ls0
Since /etc isn't part of the default search path, it only finds it with
the -c o
Here are the results from sending the trap when running snmptrapd -d:
Jul 20 08:11:27 [EMAIL PROTECTED] snmptrapd[15035]: [ID 702911 daemon.info]
Starting snmptrapd 5.1.1
Jul 20 08:12:08 [EMAIL PROTECTED] snmptrapd[15035]: [ID 702911 daemon.debug]
Jul 20 08:12:08 [EMAIL PROTECTED] Received 54 by
Here's my snmptrapd.conf:
traphandle SNMPv2-SMI::enterprises.3000.12.11
/usr/local/scripts/trapme.sh 11
traphandle SNMPv2-SMI::enterprises.3000.12.12
/usr/local/scripts/trapme.sh 12
traphandle SNMPv2-SMI::enterprises.3000.12.23
/usr/local/scripts/trapme.sh 23
traphandle SNMPv2-SMI::enterpri
It seems that any script that I put in a traphandle line in the
snmptrapd.conf file gets called twice when I send a trap to test it. So if
the script writes a value out to a file, it gets written twice. Has anyone
seen this behavior before, or know what I might be doing wrong? I'm
running net-s