On Thu, 25 Aug 2005 09:27:19 +0100 Dave wrote:
DS> On Wed, 2005-08-24 at 22:52 +0200, Magnus Fromreide wrote:
DS> This feels like a hold-over from the change to a modular transport
DS> system, which effectively deprecated the 'local_port' field. We
DS> ran into a similar problem with the handling of trap ports - this
DS> one has obviously slipped through the net.
DS>
DS> I suspect that the easiest fix will be the same approach as for the
DS> trap problem - have the AgentX master code explicitly append the
DS> default port to the transport string (assuming there isn't one
DS> there already, obviously!).
DS>
DS>
DS> Comments?
Since you asked... maybe we need a new convenience function that deals with
the new transport stuff and takes a parameter for a default, should one not be
encountered in the specified string. This could be used in several places.
It gets tricky, though. For example, trapsinks are defines as:
trapsink HOST [COMMUNITY [PORT]]
So, what if you get
trapsink tcp:localhost:4321 public 1234
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
