On 2017-04-25 17:22:37 +0200, Aurelien Jarno wrote: > While that might work (provided we keep multiple versions of the file), > I think the data are not really usable as each period will have a > different format. The real way to fix that would be to use one RRD file > per sensor, but it becomes a major change to the software, and I am not > sure we want to do that given the dead upstream
Or have a fixed config file. The sensord.cgi file (which reads the RRD file) is normally fixed, so that this would make sense. If there are new sensors, they would simply be ignored (until the user regenerates or rewrites the config file and sensord.cgi). If some sensors are no longer supported, one would simply get missing values (NaN?) in the RRD file. -- 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)
