Dave Shield wrote:
Thomas has suggested that perhaps this should be
"acceptAllNotifications" instead. That's certainly a more
technically accurate name, though I personally prefer the
one I chose (naturally, since that's why I chose it!)
Anyway - what do people think?
"acceptAllTraps", "acceptAllNotifications", or neither
(i.e. just stick with "disableAuthorization").
Whatever we agree upon, I think we should stick to *one* directive for
this purpose.
As I've already mentioned to Dave, I don't think we should introduce
*new* directives referring to "trap" when we in fact mean "notification"
(covering traps *and* informs) to not introduce additional
confusion/inaccuracy. The existing "linkUpDownNotifications" is already
a step in the right direction!
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
