Miroslav,
Wrong. The damon starts off be setting the frequency to zero, as you can
see in the protostats. When the frequency calibration is complete, the
frequency is set directly, as you can also see in the protostats. It
could be a massively broken motherboard might set the frequency larger
than 500 PPM, but in your case it set it at 172 PPM, well within the
tolerance. During the 5 minutes following the direct set, the frequency
update is suppressed, so there is no clamp. So, please explain where to
you find the bug.
Dave
Miroslav Lichvar wrote:
On Wed, Nov 03, 2010 at 03:54:33PM +0000, David L. Mills wrote:
The daemon clamps the adjtime() (sic) offset to 500 PPM, which is
consistent with ordinary Unix semantics.
No, during that new fast phase correction on start it's not clamped to
anything. That's the bug I'm hitting here.
If 500 ppm is the standard rate, Linux is working fine and
the other systems are the bad ones.
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
