On Sat, Sep 18, 2010 at 08:14:38 -0500, John Hasler wrote: > 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. Unblocked. Hopefully at some point the problem can be solved for real... Cheers, Julien
Attachment:
signature.asc
Description: Digital signature