Philipp Kern writes: > isn't there anything better than doubling the sleep timeout to > determine if chrony is indeed awake?
Patches are welcome, of course. I have had a small number of credible (but unreproducible) reports of chronyd remaining up but unresponsive for more than a second at startup. I thought that the recent upstream changes would solve the problem. They did not. While ugly, this is a known, minimum-impact workaround for a problem which is going to require source changes. -- John Hasler [email protected] Elmwood, WI USA -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
