Coders,
is there a way to have snmptrapd communicate with a *persistent* trap handler?
We're working with devices that may fire hundreds of INFORMs at once and
the current overhead of trap handler startup (for each and every INFORM) looks
prohibitive.
If this isn't currently possible, may we introduce a "traphandle_persist"
directive similar to snmpd's "pass_persist"? Would this make anyone else
rave besides me? How much work is it?
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
|
