> > It would also be useful to see a walk of the mteTriggerBooleanEvent
> > and mteTriggerBooleanEventOwner objects. It looks suspiciously as
> > if the events are set up OK, but the monitor isn't actually looking
> > for them properly.
>
> DISMAN-EVENT-MIB::mteTriggerBooleanEventOwner."snmpd.conf".'proc' = STRING:
> snmpd.conf
> DISMAN-EVENT-MIB::mteTriggerBooleanEvent."snmpd.conf".'proc' = STRING:
> amendments to the 10646 s
Yup - that's what I was expecting.
> > Please try the following patch:
[SNIP]
OK - I'm now reasonably confident that the patch should fix
your problem. It appears that I was (inadvertantly) relying
on newly-created buffers being automatically set to 0.
This works OK on Linux, but isn't universally true.
Ensuring an empty event buffer which processing the "monitor"
line ought to lead the agent to use the default built-in
events instead - as expected.
Dave
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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
