On Tue, Jan 29, 2013 at 12:13:46PM +0530, Santosh Shilimkar wrote: > To avoid the server latency, we didn't do continuous sync. The time was > synced in the beginning and after 62.5 hours (#ntpd -qg) and the drift > of about 174 ms was observed. As you said this could be because of > server sync time along with probably some addition from system calls > from #ntpd. As mentioned, the other run with HZ = 128 which started > 15 hours 20 mins is already showing about 24 mS drift now. I will > let it run for couple of more days just to have similar duration run.
Hmm. I wonder if ntpd -qg will cause ntp to read the drift file and adjust the kernel time keeping using that information... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
