The daemon says that it adjusts the time, but it doesn't... the time offset is still the same afterwards. ntpd -d -s: reply from 130.60.7.52: offset 166.672756 delay 0.005887, next query 30s reply from 141.82.30.251: offset 166.649930 delay 0.013497, next query 30s reply from 137.208.7.4: offset 166.732144 delay 0.023108, next query 30s reply from 213.174.171.174: offset 166.651898 delay 0.026631, next query 30s reply from 81.7.132.92: offset 166.648525 delay 0.026855, next query 30s reply from 130.236.254.17: offset 166.649556 delay 0.033568, next query 30s reply from 157.161.57.1: offset 166.665414 delay 0.035967, next query 30s reply from 130.206.130.95: offset 166.644716 delay 0.060068, next query 30s reply from 216.82.75.146: offset 166.658457 delay 0.133838, next query 30s reply from 24.114.130.47: offset 166.633181 delay 0.149131, next query 30s reply from 207.245.43.147: offset 166.644716 delay 0.156949, next query 30s reply from 128.208.109.7: offset 166.646879 delay 0.177768, next query 30s reply from 128.95.231.7: offset 166.647824 delay 0.177813, next query 30s reply from 63.127.106.213: offset 166.711235 delay 0.226167, next query 30s adjusting local clock by 166.684846s no reply from 146.164.48.5 received in time reply from 146.164.48.5: offset 166.634793 delay 0.257206, next query 5s reply from 146.164.48.5: offset 166.623213 delay 0.321275, next query 5s reply from 146.164.48.5: offset 166.541547 delay 0.470923, next query 5s peer 146.164.48.5 now valid reply from 146.164.48.5: offset 166.627904 delay 0.296213, next query 5s reply from 130.60.7.52: offset 166.643704 delay 0.004909, next query 30s reply from 141.82.30.251: offset 166.614345 delay 0.025899, next query 30s reply from 137.208.7.4: offset 166.701664 delay 0.026443, next query 30s reply from 81.7.132.92: offset 166.619406 delay 0.027432, next query 30s reply from 213.174.171.174: offset 166.621682 delay 0.027466, next query 30s reply from 157.161.57.1: offset 166.638658 delay 0.029559, next query 30s reply from 130.236.254.17: offset 166.620221 delay 0.033621, next query 30s reply from 130.206.130.95: offset 166.619266 delay 0.050394, next query 30s reply from 216.82.75.146: offset 166.628272 delay 0.133864, next query 30s reply from 207.245.43.147: offset 166.615805 delay 0.160769, next query 30s reply from 128.95.231.7: offset 166.621048 delay 0.170620, next query 30s reply from 128.208.109.7: offset 166.620258 delay 0.170775, next query 30s reply from 63.127.106.213: offset 166.674833 delay 0.214335, next query 30s reply from 24.114.130.47: offset 166.564156 delay 0.226325, next query 30s reply from 146.164.48.5: offset 166.610523 delay 0.263071, next query 5s Reproducible: Always Steps to Reproduce: 1. 2. 3.
test 3.7_p1
works with "ntpd -d -s", but not as daemon via "/etc/init.d/ntpd start". syslog contains message that it has adjusted time, but system time is still off. Maybe openntpd tries to set time as ntp user?
installed 3.6.x - didn't work, updated to 3.7_p1 - same situation run from console with -d -s, everything fine.
Correction: now 3.7_p1 doesn't update the system time when being run from the console, too.
In /etc/conf.d/ntpd set the following: NTPD_OPTS="-s" From the MAN page, this will: "Set the time immediately at startup if the local clock is off by more than 180 seconds. Allows for a large time correction, eliminating the need to run rdate(8) before starting ntpd." Otherwise, I think the time will be corrected *slowly*, in increments.
looks like that, thanks
