Your message dated Sat, 18 Mar 2017 17:23:14 +1100 with message-id <[email protected]> and subject line Re: snmpd reports no negative values for sensors handled by lm_sensors has caused the Debian Bug report #249904, regarding Illegal modification of LM-SENSORS MIB to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 249904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=249904 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: snmpd Version: 5.1.1-2 I noticed that I can't get negative values from my sensors. As soon as I noticed that they are all defined as unsigned ints, it became quiet clear to me. I redefined them where appropriate (see attached patch). Every sensor type except fan speed sensors should be able to hold a negativ value. That includes temp, voltage and misc sensors. Ok, for temp sensors a negative value is really unlikely, but more likely than such a high readout that we need a full 2^32 bit value. I guess in such a case there isn't much left to monitor anyway ;). And for the others I think it's quite clear that they could hold negative values. I modified the code and the MIB file (hope that we're all places). cheers, Peter --------------------------------------------------------------------- Peter Hirdina Frauenstrasse 128 [email protected] 89073 Ulm / Germany --------------------------------------------------------------------- PGP Key available, send request to [email protected] ---------------------------------------------------------------------
net-snmp-5.1.1-2.lm_sensors.negative-values.patch
Description: Binary data
--- End Message ---
--- Begin Message ---Hi, I have recently taken over the Debian maintainership of net-snmp. This is a rather old bug but I have looked into it. The value of SNMP MIBs is that everyone has the same (or close to the same) response. As mentioned prevously, we cannot change a MIB definition once it is published; only extend it. Upstream said about 7 years ago they would look at it for version 5.1 and we are now in 2017 with version 5.7.3 For this change to happen the MIB would need to be redefined or a new one created THEN the code would need to be changed upstream. Until there is a new or updated MIB published, we are unable to implement a changed behaviour. It looks like its not going to happen given the 7 year silence, so I am closing this bug. - Craig -- Craig Small (@smallsees) https://dropbear.xyz/ csmall at : enc.com.au Debian GNU/Linux https://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
--- End Message ---
