On Tue, 2006-01-24 at 17:46 +0530, Rane, Prashant wrote:
> But this snmptrapd binary cores when I try to run it with the "debug
> all" option , as seen below
As Thomas has said, we'd really need to see a debugger back trace
to comment on why this might be failing (let alone fix it).
We'd probably also need to know what options you gave to "configure"
when compiling the software.
Does this happen if you *don't* turn on debugging?
(or don't turn on *all* the debugging statements, which produces
a looooot of output!)
> # ./snmptrapd -D ALL -Lo
When testing, I'll typically run with
./snmptrapd -f -Le
and just enable the particular debugging tokens that I'm
actually interested in.
Dave
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
