Hi, On 2015-08-08 23:30:26 +0200, Aurelien Jarno wrote: > From what I have been able to get the problem is that when using a > single rrd file for all data, the number of columns (ie sensors) is > defined when the file is created. Therefore the upgrade of your kernel > changed the number of sensors, and caused this issue. > > From what I have been able to read in the documentation, one solution > would be to use the MULTIPLE mode of RRD, which create one file per > column or sensor. But this format is incompatible with the current one, > which means people will have to recreate their database, and possibly > the scripts extracting the data for them.
This could be an option (set by default to avoid problems in the future). But anyway, after upgrading the kernel (even a security update!), the database is currently no longer usable. So, this would not be worse than the current situation. > I don't really know what is the solution for this bug, one might be to > stop shipping sensord in Debian as it is kind of dead upstream and not > build by default. Is there a replacement? Or perhaps it's easy enough for the user to write a daemon in a shell/Perl/whatever script by executing the sensors utility. BTW, I already have written such a utility in Perl, which supports CPU load, disk usage and entropy. Adding sensors support would really be easy. -- 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) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
