On fre, 2007-12-21 at 16:31 +1100, Ben Nizette wrote: > > In fact I had tried using TCP and it used to fail with the "no support > for any checked transport domain" cruft. I just got the guy who > compiled net-snmp for me to email across the configure line he used and > for reasons best know to himself, he had added TCP to the > --with-out-transports clause. This has been recitifed, he's been > slapped and the communication now seems to be working just about fine :-)
Great. > What ever the problem with sockets is, it's a different one, that > transport was built in. But not to worry. Yes, but it is interesting as it should work. If you add the flag -Dtdomain,netsnmp_unix_transport to the subagent then it will say what transports it tries and what arguments it feeds them and enable the logging in the unix transport as well, this could help tracking down the problem. > I donno, if you want something done right, do it yourself eh? ;-) :-) /MF ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
