snmptrapd - "Event" handling

I've been working on updating the documentation for 'snmptrapd',
and have eventually got round to tracking down exactly what
is the purpose of the 'printEventNumbers' directive (and the
"Event" handling code).

I was horrified to realise that this is special-case processing
for displaying three traps defined in the Manager-to-Manager MIB
(RFC 1451) which was part of the early (unsuccessful) SNMPv2 work.
Checking the trapd code, this trap handling has remained
essentially untouched for the last 11 years!


I suggest that this "feature" is completely obsolete, and should
be withdrawn as soon as possible. I'm not sure whether it's
sensible to delete the code completely just at the moment, since
we're in Release Candidate mode. But I would like to start to
deprecate this code - preferably by withdrawing the '-e' option
and 'printEventNumbers' directive.

I'm therefore calling for votes on such a proposal.

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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders