"Wei, Catherine" writes: > Hello: > > I met an sntp sync time problem. Not sure if it's related to the upgrade > of ntp. I logged on to a linux embedded box as root, and the time is > > "Thu Jan 1 16:10:15 CET 1970" > > > Then I used sntp command: > > "/usr/sbin/sntp -l /tmp/sntp.log -t 10 10.204.134.250 -s" > > > I got the following result: > > " > > sntp [email protected] Thu Feb 16 09:54:19 UTC 2017 (1) > kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or d > irectory > 1970-01-01 16:04:55.269888 (-0100) +1487240461.813365 +/- 991493641.349652 10 > .204.134.250 s3 no-leap? > > " > > > Considering the warning in the second line, I did some research and it was ju > st a file used for the persistent history of KoD??, it just types a warning. > I don't think this will affect the time sync.
It is just a warning and will not affecet time sync. > According to the last line in the result, it prints out the offset in seconds > , it seems that the print result is good, but the system time is not synced a > fter You used -s, which slews the correction. The correction is underway, but a 500ppm slew corrects a 1 second change in about 33 minutes. So it's gonna take a while. I'm not sure why you're using sntp instead of running ntpd, but you might want to use -Ss instead. H -- > I used the sntp command. > > > Can anyone helps me with that? Appreciate it. It bothered me for several days > . Thank you very much. > > > > > Catherine, > > Best regards > _______________________________________________ > pool mailing list > [email protected] > http://lists.ntp.org/listinfo/pool > _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
