change in ntpd behavior

2019-10-23 Thread Paul de Weerd
Hi all, While scanning my logs for something unrelated, I came across this message from ntpd (note that I have ntpd_flags set to '-v' in /etc/rc.conf.local): 2019-10-21T02:03:50.143Z despair ntpd[57871]: adjusting local clock by 5.579152s I found it weird, because the machine had been up for alm

Re: change in ntpd behavior

2019-10-23 Thread Otto Moerbeek
On Wed, Oct 23, 2019 at 09:57:49AM +0200, Paul de Weerd wrote: > Hi all, > > While scanning my logs for something unrelated, I came across this > message from ntpd (note that I have ntpd_flags set to '-v' in > /etc/rc.conf.local): > > 2019-10-21T02:03:50.143Z despair ntpd[57871]: adjusting local

Re: change in ntpd behavior

2019-10-23 Thread Paul de Weerd
Hi Otto, On Wed, Oct 23, 2019 at 10:58:24AM +0200, Otto Moerbeek wrote: | I could * this has to do with the logging changes. Previously, debug | messages could disappear because of wrong logging setup. In non -v | mode, only big adjustments are logged. Sadly you stripped those | numbers away so i

Re: change in ntpd behavior

2019-10-23 Thread Otto Moerbeek
On Wed, Oct 23, 2019 at 11:17:02AM +0200, Paul de Weerd wrote: > Hi Otto, > > On Wed, Oct 23, 2019 at 10:58:24AM +0200, Otto Moerbeek wrote: > | I could * this has to do with the logging changes. Previously, debug > | messages could disappear because of wrong logging setup. In non -v > | mode, on

Re: change in ntpd behavior

2019-10-23 Thread Paul de Weerd
On Wed, Oct 23, 2019 at 11:43:25AM +0200, Otto Moerbeek wrote: | On Wed, Oct 23, 2019 at 11:17:02AM +0200, Paul de Weerd wrote: | | > Hi Otto, | > | > On Wed, Oct 23, 2019 at 10:58:24AM +0200, Otto Moerbeek wrote: | > | I could * this has to do with the logging changes. Previously, debug | > | me

Re: change in ntpd behavior

2019-10-23 Thread Claudio Jeker
On Wed, Oct 23, 2019 at 11:17:02AM +0200, Paul de Weerd wrote: > Hi Otto, > > On Wed, Oct 23, 2019 at 10:58:24AM +0200, Otto Moerbeek wrote: > | I could * this has to do with the logging changes. Previously, debug > | messages could disappear because of wrong logging setup. In non -v > | mode, onl

Re: change in ntpd behavior

2019-10-23 Thread Mark Kettenis
> Date: Wed, 23 Oct 2019 11:43:25 +0200 > From: Otto Moerbeek > > On Wed, Oct 23, 2019 at 11:17:02AM +0200, Paul de Weerd wrote: > > > Hi Otto, > > > > On Wed, Oct 23, 2019 at 10:58:24AM +0200, Otto Moerbeek wrote: > > | I could * this has to do with the logging changes. Previously, debug > > |

Re: change in ntpd behavior

2019-10-23 Thread Paul de Weerd
Hi Mark, Claudio, Thanks for your replies. On Wed, Oct 23, 2019 at 12:07:22PM +0200, Mark Kettenis wrote: | This may be a consequence of the timecounter choice. Did the output | of kern.timecounter change on this machine? | | What is the output of sysctl kern.timecounter in this state? On Wed,

Re: change in ntpd behavior

2019-10-27 Thread Paul de Weerd
On Wed, Oct 23, 2019 at 01:00:59PM +0200, Paul de Weerd wrote: | So, before I was also using tsc. I've now changed to acpihpet0 and | will see if that helps at all. I still see a lot of clock adjustments after having switched to acpihpet0: 1 despair ntpd[57871]: adjusting local clock 1 de