On 2017-01-29 15:54:36 +0000, Andy Simpkins wrote: > Back in August *2015* there was a short discussion regarding removing > sonsord from lm-sensors as a result of this bug. > > Because it is marked as GRAVE, this bug is release critical for Stretch. > > Is this really a grave bug, should it be down graded?
This is data loss. Downgrading the bug would be a bad idea. Why not just simply fix it? > Can Sensord be removed? If it is too broken and unfixable, then it should be removed, which would be a simple way (though not the best way) to fix the bug as a consequence. What's the point of keeping something that no longer works? > Is there another option? > > It seams to me that if you depend on the structure of a file that > changes you could simply re-initialise sensord passing it the new > structure. What do you mean? Note that rebooting the machine doesn't solve the problem. On a different machine, I still have: [...] Jan 29 21:35:00 ypig sensord: Error updating RRD file: /var/log/sensord.rrd: /var/log/sensord.rrd: found extra data on update argument: 0.040000 Jan 29 21:35:00 ypig sensord: rrd update error (-1) Jan 29 21:40:00 ypig sensord: Error updating RRD file: /var/log/sensord.rrd: /var/log/sensord.rrd: found extra data on update argument: 0.000000 Jan 29 21:40:00 ypig sensord: rrd update error (-1) Jan 29 21:45:00 ypig sensord: Error updating RRD file: /var/log/sensord.rrd: /var/log/sensord.rrd: found extra data on update argument: 0.140000 Jan 29 21:45:00 ypig sensord: rrd update error (-1) -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
