06.02.2019 3:55, Ian Lepore wrote: > So your problem was most likely the gps receiver making a bad choice > before it had enough info to make a good choice. It's one of many > reasons why an ntp server should have at least 3 (really, at least 5) > peers, so it can reject obviously-insane data from a single source. > Even when you use a gps to get really accurate local time, you should > have a handful of network peers that can serve as sanity-checkers.
And I have and had that moment: driftfile /var/db/ntpd.drift server Time2.Stupi.SE iburst maxpoll 9 server ntp1.sp.se iburst maxpoll 9 server ntp1.mmo.netnod.se iburst maxpoll 9 server ntp1.ptb.de iburst maxpoll 9 server ntp1.ien.it iburst maxpoll 9 server ntp1.sth.netnod.se iburst maxpoll 9 server 127.127.1.0 fudge 127.127.1.0 stratum 10 # Had to comment out following 3 lines after the incident #tos mindist 0.015 #server 127.127.20.1 mode 1 iburst maxpoll 9 prefer #fudge 127.127.20.1 stratum 10 time1 0.000 time2 0.000 flag1 1 flag3 1 refid PPS pool 0.freebsd.pool.ntp.org iburst restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery restrict 127.0.0.1 restrict ::1 leapfile "/var/db/ntpd.leap-seconds.list" _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
