David Woolley wrote:
David Lord wrote:
For me using "iburst" for server line and "ntpd -q" before
starting ntpd will get within 10ms or so. With just two servers
Not with standard parameters. Standard parameters will only get you
within 128ms, unless the error was more than 128ms to start with.
sudo ntpq -p
serv1 192.168..... 2 u 53 128 377 0.535 21.891 2.791
serv2 .MSFa. 2 u 8 128 377 0.359 20.134 1.709
serv3 192.168..... 2 u 125 128 377 0.666 19.719 1.385
sudo /etc/rc.d/ntpd stop
sudo ntpd -q
ntpd: time slew +0.008954s
sudo ntpd -q
ntpd: time slew +0.005993s
sudo ntpd -q
ntpd: time slew +0.000084s
sudo /etc/rc.d/ntpd start
ntpq -p
serv1 192.168..... 2 u - 64 1 1.678 0.569 0.219
serv2 .MSFa. 1 u - 64 1 1.565 0.545 0.180
serv3 192.168..... 2 u - 64 1 1.723 0.899 0.678
ntpq -p
serv1 192.168..... 2 u - 64 177 0.457 1.272 1.774
serv2 .MSFa. 1 u - 64 177 0.310 1.262 1.668
serv3 192.168..... 2 u - 64 177 1.378 2.153 1.656
Drift file was out at start and offset increasing
David
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
