Robert Story wrote:
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?
The ipaddress portion (which I thought I said ;-)).
Probably the documentation needs updating, as it's conceivable that someone
could be running over a transport that doesn't use ip addresses.
The new format undoubtly offers advantages, but the main problem of
course is backward-compatibility. We may want to introduce a config
setting to switch between the two (defaulting to old behaviour until at
least 5.4).
But I think the space between the transport and the address is probably a bug.
Does it still come in as a single parameter?
Sure, because the delimiter that matters is a newline, not white space.
+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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
