Hi John, I think I am experiencing a problem which seems to be closely related to this problem.
On a box where /etc/resolv.conf is: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 and the DNS is provided by dnsmasq (on the box itself), chrony fails to produce any log in /var/log/chrony/{tracking|statistics|measurements}.log which stay zero-length files. Chrony suddenly begins working properly when it is manually restarted after the boot is over. By looking at the dependency-based boot order, it seems that chrony is started before dnsmasq, that is to say, when DNS is not yet available. $ ls /etc/rc2.d/ | grep 'dns\|chrony' S01chrony S02dnsmasq I think that adding a Should-Start: $named to the LSB init headers of /etc/init.d/chrony could mitigate this bug. What do you think? Is it a good idea? P.S.: while testing LSB init header changes, please remember to consider following the suggestion by Michael Meskes in #541806, as well... -- New location for my website! Update your bookmarks! http://www.inventati.org/frx ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgpvbtTFH4fPZ.pgp
Description: PGP signature