![]() | ||||||||||
Messages in this thread |
On Sat, Apr 12, 2008 at 12:09 AM, Marc Perkel <mperkel@yahoo.com> wrote: > > Is it possible due to calibration that ntpd isn't able > to correct the problem? Is there a setting to make ntp > more agressive? Clock crystals typically have an error between 20 and 200 ppm. ntpd can correct clock crystal errors of maximum 500 ppm. If I remember correctly the kernel limits frequency adjustments to 512 ppm. It's not a good idea to try to change this limit -- large clock crystal errors slow down convergence of ntpd's algorithms significantly. Bart. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2008-04-13 10:21 [from the cache] ©2003-2008 | ||||||||||