Package: chrony Version: 1.23-6+lenny1 After upgrading chrony (from 1.23-6), I find the log message "Could not open driftfile /var/lib/chrony/chrony.drift for reading". Also, for a while the drift frequency, as reported by "chronyc tracking", is stuck at 0.0. (I have one machine whose drift frequency needs to end up around -10000, so this leads to several dozen "System clock wrong ... adjustment started" log messages in an hour.)
This might be a result of the first command in chrony.postrm, "rm -f /var/lib/chrony/*". Is it desirable for this useful data to be forgotten upon each upgrade? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
