On Sat, 22 Sep 2007, Guillaume Filion wrote: > Hi, > > It seems that my local server is wrong by a few ms, and when I look at > ntpq it's fairly obvious that the selection algorighm selected a server > that is off by 8 ms. I added another statum 1 server (204.123.2.5) but > ntpd insists on choosing the one that is 8 ms off. > > Any idea what's going on? I'm wondering if there's something basic that > I don't understand in the algorithm. > > [EMAIL PROTECTED]:~$ ntpq -pn > remote refid st [...] delay offset jitter > ================================================================== > -132.214.200.120 18.26.4.105 2 [...] 20.217 -5.729 0.877 > +132.246.168.164 132.246.168.2 2 [...] 16.983 -5.172 0.058 > *208.184.49.9 .ACTS. 1 [...] 41.468 4.369 0.477 > +204.123.2.5 .GPS. 1 [...] 99.864 -4.133 0.098 > 127.127.1.0 .LOCL. 13 [...] 0.000 0.000 0.001 > 192.168.0.255 .BCST. 16 [...] 0.000 0.000 0.001 > 10.10.16.255 .BCST. 16 [...] 0.000 0.000 0.001 > > (I removed a few columns to prevent line wrap...)
I beleive that ntpd will choose the server that has the closest time from your kernel time when you start ntpd up. Just run ntpdate with the server you want ntpd to pick up before starting ntpd. That should do it. -ls > > Thanks, > GFK's > -- > Guillaume Filion > http://guillaume.filion.org/ > > Louis http://blogtech.oc9.com _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
