On Sat, Aug 27, 2016 at 08:28:33PM +0200, Vincent Blut wrote: > Hi, > > Currently, the measurement history is persistent for each sources no matter > if it is inspected by chronyd afterward. This persistence might cause some > staled measurements. Thus, I think it would be nice to have a clean way > (meaning not having to write a shell script ;-) ) to deal with those old > measurements. So, what about implementing a dedicated chronyc option (or > passing an option to the dump command) to manage that task?
Good question. I think it would be nice if old dump files were removed automatically in order to prevent loading old/invalid data and also avoid creating mess in the dumpdir when using servers that change addresses frequently (e.g. pool.ntp.org). When the system clock is adjusted, all dump files are immediately invalid (even if they were not loaded), so we might want to remove all *.dat files in the dumpdir when chronyd is started (after loading some of them or maybe none). I suspect there could be a problem if someone has configured chrony to share the dumpdir with some other program that creates *.dat files and chronyd would remove files it didn't create. I guess it should be ok if we check the filenames first if they contain refid/IP address as chronyd names its dump files. I'll look into this. Thanks for the suggestion. -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.