From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020606 Description of problem: The client, LLNL, needs to have lm_sensors support for the ucd_snmp snmpd. A long time ago RH supplied an unsupported patch which provides this functionality. They would like to roll this into the main distribution but lm_sensors is exceedingly dangerous on some systems. Evidently it can burn out a thinkpad or something like that. So LLNL had me code up a way that the same binary can be used on a system with or without lm_sensors. What I did was use dlopen to load the sensors library if it exists. If not then that part of the mib is never even registered. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.snmpwalk host community host.hrSensors Actual Results: no sensor readings are listed Expected Results: sensor readings are listed Additional info: Let me know if I need to make more sophisticated logic for deciding when to use the lm_sensors functionality.
Created attachment 65708 [details] The original usupported lm_sensors patch
Created attachment 65709 [details] The patch that I coded up which dlopens the lm_sensors library
The sensor-dl.patch applies on top of the sensor.patch. The spec file modifications were extremely minor. I simply added, the patch to the sources list and to the prep section. The patch applies with -p1.
James Antill posits that it is weird to have a piece of software change behavior simply because another package is installed. He suggested adding a configuration option which would try to enable that functionality. If that functionality is not available i.e. snmpd cannot load the library or resolve all the symbols then spit out something to syslog.
Errata packages have been done, waiting for QA to pick them up and finalize them. Read ya, Phil
*** Bug 76509 has been marked as a duplicate of this bug. ***
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2002-159.html