I am developing a subagent for our product which will be deployed on
different Linux platform (redhat 3,4/Suse 9,10).
Our devlopment platfom is redhat enterprise 3 which uses net-snmp 5.0.9. the
"net-snmp-config --agent-libs" returns the follwowing result:
-L/usr/lib -lnetsnmpagent -lnetsnmpmibs -lnetsnmphelpers -lnetsnmp -ldl
-lrpm -lrpmio -lpopt -lbz2 -lz -lcrypto -lelf -lm -L/usr/lib/lib -lwrap
So our product links the following share libraries:
libnetsnmpmibs.so.5
libnetsnmpagent.so.5
libnetsnmphelpers.so.5
libnetsnmp.so.5
librpm-4.2.so
libwrap.so.0
After deploying our product to Suse 10, I got the following problems:
1) first, our product find the above libraries because Suse 10 uses net-snmp
5.3.1 which changes the name of those libraries.
2)So I add some symbol links to those libraries. Now I got a new error:
"/usr/lib/libnetsnmpmibs.so.5: undefined symbol: sensors_get_label
I did a lot test, and I found it is because the default net-snmp 5.3.1 has
the configuration opiton "ucd-snmp/lmSensors".
So I recompile our products with this MIB support. Now It works again.
But the problem is what if the net-snmp on the target platform does not have
the option "ucd-snmp/lmSensors" and even the platform doesn't install
package lm_sensors?
Why must we link those third-party libraries when developming agent? I think
it will make any cross-platform can't use net-snmp.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
