Christian Weisgerber writes: > On 2016-02-06, Lampshade <[email protected]> wrote: > > > Feb 6 17:57:25 host ntpd[7585]: peer 150.254.183.15 now valid > > Feb 6 17:58:17 host ntpd[9279]: adjusting local clock by 9.096751s > > Feb 6 18:02:02 host ntpd[9279]: adjusting local clock by 7.971861s > > > I don't think that clock is adjusted "by" that values. > > It is.
There is a difference between "how much the clock is adjusted by", which is implied by "is adjusted by", and "how much the clock needs to be adjusted by", which is what's being done. The message is the best kind of correct but could be clearer by either including the amount of adjustment occuring at the time the message is logged or distinguishing between "the amount that the clock needs to be adjusted" and "the amount that the clock is being adjusted by right now", eg. "adjusting local clock by <n>ms out of <y>s" - or - "local clock <y>s out of sync; skewed <n>ms (forwards|backwards)" Whether clarifying this message lies within the purview of openbsd ports is another matter. Matthew
