Re: snmptrapd - avoiding ambiguity in log files

Thomas Anders <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
Don Cohen wrote:
>  # ./net-snmp-5.1.3.1/apps/snmptrapd -f -c /tmp/snmptrapd.conf
> where /tmp/snmptrapd.conf contains:
>  traphandle default /tmp/snmptraphandler
> and I get
>  No log handling enabled - turning on stderr logging
>  Cannot find module (IP-MIB): At line 0 in (none)
> ...
> and output similar to the first case above without -c,
> but no call to /tmp/snmptraphandler.
> This did work in 5.0.9.

For a test, only put "trapdhandle default /bin/cat" into your 
snmptrapd.conf and run snmptrapd with "-Drun:exec" (in addition to "-f 
-Lo -C -c ...". It should print something like:

run:exec: running '/bin/cat'
run:exec:   child 29893 finished. result=0

when it gets a trap. Does it? If so, try to move forward one change at a 
time.


+Thomas

-- 
Thomas Anders (thomas.anders at blue-cable.de)


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.