On Tue, 17 Jan 2006 00:56:08 +0100 Thomas wrote:
TA> the traphandle interface as documented in snmptrapd.conf
TA>
TA> HOSTNAME
TA> IPADDRESS
TA> VARBINDS
TA>
TA> seems to be broken in 5.2.2, 5.3 and 5.3.0.1 (and MAIN). The IPADDRESS
TA> part now is (e.g.) "UDP: [10.11.12.13]:161" instead of "10.11.12.13"
TA> which is not unlikely to break expectations of existing notification
TA> handlers.
Is that the hostname or ipaddress portion?
Probably the documentation needs updating, as it's conceivable that someone
could be running over a transport that doesn't use ip addresses.
But I think the space between the transport and the address is probably a bug.
Does it still come in as a single parameter?
--
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.
-------------------------------------------------------
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
