-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Rob Janssen wrote: > Also, during initial experiments, when you stop and start ntpd all the > time (because the sucker cannot reload a config file without restarting, > much like old versions of Windows), it usually gets confused because > more than one time adjustment is ongoing in the kernel. The result is > that it wanders around the desired time, suddenly jumps a big fraction > of a second, loses lock, etc etc. Bad things. > This stops happening when you don't touch it for a couple of hours. So > don't keep fiddling until you get desperate, but just edit the config to > arrive at something like the above and then leave it alone for a day to > see what ntpq -p looks like (instead of looking every minute and asking > yourself what it is doing). > That makes so much sense as to why whenever I restart ntpd I will see this HUGE (read: 1-4 msecs) spike and it always confused me on the cause. - -- Todd http://www.vrillusions.com/ My PGP Key ID: 0xBC90230C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHD7xeiSebwryQIwwRAhplAJ0UtHer6SsPnZ16jUeiSbTJ9EjmVgCeLEPD J+/aUJRMaYe3P0xpLw8gXC4= =ELIE -----END PGP SIGNATURE----- _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
