@lanodan @syzygy

> I think by default chrony sets the clock at launch and then drifts.

Yep, this is what the docs indicate, this is exactly the behavior I want (and apparently they use the ethernet hardware timestamps). ntpd tries to guess at and anticipate drift and then jump to the target time in 250ms increments. As far as I can tell, it has never done that correctly, or those clocks would get *closer* together rather than one of them speeding up and one slowing down.

> it adjusts by steps of 0.1 seconds unless it's bigger than 3 seconds.

Yeah, reasonable.